Back to Nodes

Nimply

Last updated Oct 31, 2026

n8n community nodes for Nimply.io — run AI social media agents, automations and designs, and schedule, approve, publish and measure posts

216 Weekly Downloads
283 Monthly Downloads

Included Nodes

Nimply
Nimply Trigger

Description

@nimply/n8n-nodes-nimply

This is an n8n community node package for Nimply, the AI social media workforce. Hire and run AI agents, build automations, create designs, and schedule, approve, publish and measure posts across Facebook, Instagram, X/Twitter, LinkedIn, TikTok, YouTube, Pinterest, and more.

It contains two nodes:

  • Nimply — run agents and automations, create designs and brand kits, create, approve, schedule and publish posts, manage media and link pages, and read analytics.
  • Nimply Trigger — start workflows when events happen in your Nimply workspace (post published, post failed, approval requested, new lead, …).
  • n8n is a fair-code licensed workflow automation platform.

    Installation

    Follow the installation guide in the n8n community nodes documentation:

    1. In n8n, go to Settings → Community Nodes.
    2. Select Install.
    3. Enter @nimply/n8n-nodes-nimply and confirm.

    For a self-hosted manual install:

    npm install @nimply/n8n-nodes-nimply
    

    Credentials

    The nodes use the Nimply API credential type:

    1. In the Nimply app, go to Settings → Developers and create an API key (nimlive...).
    – Tick the scopes for what your workflows do:

    | Area | Scopes |
    | — | — |
    | Posts | posts:read; posts:write to create, update and approve; posts:publish to publish (now, next_slot, or a time) |
    | Channels, media, analytics, workspace | channels:read, media:read / media:write, analytics:read, workspace:read |
    | Link pages | links:read, links:write |
    | Agents | agents:read, agents:write (hire, change, remove), agents:run (run, cancel) |
    | Automations | automations:read, automations:write |
    | Designs and brand kits | designs:read, designs:write |
    | Trigger | webhooks:manage |
    2. In n8n, create a new Nimply API credential and paste the key.
    3. Leave Base URL at https://api.nimply.io unless you are testing against another environment.

    The credential is verified against GET /v1/workspace.

    Operations

    Nimply node

    | Resource | Operation | Description |
    | — | — | — |
    | Post | Create | Create a post on one or more channels (draft, next_slot, now, or a specific datetime) |
    | Post | Create Bulk | Create up to 50 posts in one request |
    | Post | Create YouTube Video | Upload a video or Short with full YouTube options — category, visibility, license, subscriber notification, embedding, made-for-kids, AI-made content label |
    | Post | Create TikTok Post | Post a video or photos with comment/Duet/Stitch settings and commercial-content disclosure, or send it to the creator’s TikTok drafts |
    | Post | Create Pinterest Pin | Create a pin on a specific board (picked from a live dropdown) with a destination link and alt text |
    | Post | Create LinkedIn Post | Post to a profile or company page with visibility control (public or connections only) |
    | Post | Request Approval | Send a draft for approval |
    | Post | Approve | Approve a post waiting for approval, with an optional comment |
    | Post | Reject | Send a post back with feedback |
    | Post | Get | Get a single post |
    | Post | Get Many | List posts, filterable by status and channel (cursor pagination handled for you) |
    | Post | Update | Update the content/title of a draft or scheduled post |
    | Post | Delete | Delete a draft or scheduled post |
    | Post | Schedule | Set or change when a post will publish |
    | Post | Unschedule | Move a scheduled post back to draft and clear its publish time |
    | Post | Publish | Queue a post for immediate publishing |
    | Channel | Get | Get one connected channel |
    | Channel | Get Many | List connected channels |
    | Channel | Get Schedule | Get a channel’s posting time slots per weekday |
    | Media | Upload From URL | Import a file from a public URL into workspace storage |
    | Media | Upload Binary | Upload binary data from a previous node (Drive, FTP, …) via a presigned URL |
    | Media | Get | Get one media asset |
    | Media | Get Many | List media assets, filterable by type |
    | Media | Delete | Delete a media asset that no post or design uses |
    | Analytics | Get Workspace Analytics | Aggregated metrics across all channels for a date range |
    | Analytics | Get Channel Analytics | Daily profile metrics for one channel |
    | Analytics | Get Post Analytics | Daily metric snapshots for one post |
    | Link Page | Get Many | List the workspace’s nimply.link pages |
    | Link Page | Get | Get a page with its blocks |
    | Link Page | Add Block | Add a link button, text, section, post card, product, coupon, countdown, notice bar, FAQ or testimonial block (optionally publish right after) |
    | Link Page | Update Block | Replace a block’s config, switch it on/off, or set its schedule window (optionally publish right after) |
    | Link Page | Delete Block | Remove a block from a page |
    | Link Page | Get Analytics | Views and clicks for the last 7 days, 28 days or 12 months |
    | Link Page | Publish | Publish the page draft so changes go live at nimply.link |
    | Agent | Get Templates / Get Template | List the agents you can hire, and the setup fields each one asks for |
    | Agent | Hire | Hire an agent from a template on your channels |
    | Agent | Get / Get Many | Get your agents, filterable by status and template |
    | Agent | Update | Rename, pause or resume an agent, or change its settings and channels |
    | Agent | Remove | Remove an agent |
    | Agent | Run | Run an agent now and (optionally) wait for the result. Uses AI credits; output lands as posts awaiting approval |
    | Agent | Get Run / Get Runs / Cancel Run | Check, list or stop runs |
    | Automation | Get Recipes / Get Step Types | List ready-made recipes and the triggers and actions you can use |
    | Automation | Create From Recipe / Create | Create an automation as a draft, from a recipe or from a list of steps |
    | Automation | Get / Get Many / Update / Delete | Manage automations |
    | Automation | Test | Try an automation with sample data; nothing is posted or sent |
    | Automation | Switch On / Pause / Run | Switch an automation on or off, or run it now |
    | Automation | Get Run / Get Runs | See what each step did |
    | Design | Create From Prompt | Design a post or carousel (up to 7 slides) from a short brief, in your brand kit’s look, and (optionally) wait for it. Uses AI credits |
    | Design | Create From Image | Turn an image into an editable design with separate layers. Uses AI credits |
    | Design | Estimate Credits | See the most credits a run can use before starting it |
    | Design | Get / Get Many / Get Job / Cancel Job / Get Sizes | Designs, job progress and the available sizes |
    | Brand Kit | Get / Get Many / Create / Update | Colours, fonts, logo, voice and guidelines |
    | Brand Kit | Import From Website / Import From Sources / Get Import / Save Import | Build a kit from a website, notes, a PDF brand book, a channel or images |
    | Brand Kit | Add Look Examples / Learn Look / Get Look / Set Look Rules | Teach a kit your brand’s look from your own images and posts |
    | Workspace | Get | The workspace your API key belongs to |

    #### Agents and designs run in the background

    Agent → Run, Design → Create From Prompt and Design → Create From Image start a job that takes from a few seconds to a few minutes. With Wait for Completion on (the default), the node waits (up to Max Wait) and returns the finished run or job. Turn it off to return straight away, then check later with Get Run / Get Job.

    Agents never publish on their own: what they make lands in Nimply as posts awaiting approval. Use Post → Approve when you are ready. Settings that skip a human check (auto-reply, agent auto-scheduling, comment-to-DM auto-send) can only be switched on in the Nimply app; the API refuses them with SETINAPP.

    #### Platform-specific posting

    The generic Create operation covers the fields every platform understands. For
    platforms with their own options, use the dedicated operations instead — they expose the
    full option set with dropdowns populated live from your account:

  • Create YouTube Video — title (required), video or Short, category, visibility (public/unlisted/private), license, notify subscribers, allow embedding, made for kids, contains AI-made content.
  • Create TikTok Post — allow comments/Duet/Stitch, branded-content and your-brand disclosure, or Send to TikTok Drafts to finish the post in the TikTok app (the only option for private accounts). TikTok posts publish publicly; the old privacy-level setting is no longer used.
  • Create Pinterest Pin — board (required; picked from the channel’s boards), title, description, destination link, alt text.
  • Create LinkedIn Post — content (required), media, visibility (public or connections only).
  • Facebook, Instagram, X/Twitter, and Threads have no extra options — use the generic Create operation for those.

    Nimply Trigger node

    Subscribes a Nimply webhook to your workflow and fires on the selected events:

    post.created, post.updated, post.published, post.failed, post.deleted, post.approvalrequested, post.approved, post.rejected, channel.connected, channel.disconnected, lead.created, lead.stagechanged

    The webhook is created when the workflow is activated and removed when it is deactivated. Every delivery is verified against the X-Nimply-Signature header (HMAC-SHA256) using the signing secret returned at webhook creation; deliveries with a missing or invalid signature are rejected with 401.

    Example workflows

    Ready-to-import workflows live in examples/. To use one, open the JSON file, copy all of it, click into an empty n8n canvas and paste (Ctrl/Cmd+V). Then attach your Nimply API credential to the Nimply nodes and pick your own sheet, Slack channel or CRM URL.

    | File | What it does |
    | — | — |
    | agent-from-sheet-row.json | New Google Sheets row → Agent → Run with the row’s topic → Slack message saying how many drafts are waiting for approval |
    | lead-to-crm.json | Nimply Trigger: lead.created → HTTP Request that sends the lead’s name, email, phone and profile to your CRM |
    | post-failed-alert.json | Nimply Trigger: post.failed → Post → Get → Slack alert with the post text and the reason it failed |

    Run an agent and use its drafts

    Agent → Run with Wait for Completion on returns the finished run:

    {
      "id": "5b1c…",
      "agentId": "a3f9…",
      "status": "COMPLETED",
      "creditsUsed": 12,
      "outputs": { "postIds": ["7a24…", "9c01…"], "designIds": [], "ideaIds": [] }
    }
    

    Pass input from earlier nodes with an expression in Input (JSON):

    {{ JSON.stringify({ topic: $json.topic, sourceUrl: $json.link }) }}
    

    To approve the drafts from the workflow (for example after someone replies in Slack), add n8n’s Split Out node on outputs.postIds, then Post → Approve with Post ID set to {{ $json.postIds }}.

    Create a carousel design

    Design → Create From Prompt with Format: Carousel and Wait for Completion on returns the finished job. Each design has an edit link and preview images:

    {
      "id": "6a1f…",
      "status": "done",
      "creditsCharged": 140,
      "designs": [
        {
          "id": "d81e…",
          "name": "Autumn menu",
          "pageCount": 5,
          "editUrl": "https://app.nimply.io/…",
          "previewUrls": ["https://…/1.png", "…"]
        }
      ]
    }
    

    Use Design → Estimate Credits first, or set Max Credits, to cap what a run can spend.

    React to webhook events

    Every Nimply Trigger delivery has the same envelope. Branch on type and read data:

    {
      "id": "evt_56e4…",
      "type": "lead.created",
      "createdAt": "2026-10-31T09:12:00.000Z",
      "workspaceId": "d838…",
      "data": {
        "lead": { "id": "…", "name": "Sara Malik", "platform": "INSTAGRAM", "stage": "NEW", "contact_email": "[email protected]" }
      }
    }
    

    post.* events carry data.postId, data.channelId, data.status and, for post.failed, data.error.

    Upgrading from 0.4.x or earlier

  • Create TikTok Post no longer has the required Privacy Level field. TikTok ignores it now; existing workflows keep working without changes.
  • Compatibility

    Requires n8n 1.x and Node.js >= 18.10.

    Resources

  • Nimply API documentation
  • n8n community nodes documentation

License

MIT

From our network Other tools and sites we build