Zapier is where most teams already keep their glue: the automations that move data between forms, spreadsheets, CRMs, and chat tools. Social media posting is usually the odd one out, handled by hand in a separate tab. The Nimply app for Zapier closes that gap — any of the thousands of apps in your Zapier account can now create, schedule, and manage social posts.
It works in both directions. Actions let a Zap draft a post, drop it into your next free posting slot, publish immediately, or schedule it for an exact time — across Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, and Threads. Triggers fire instantly when something happens in Nimply, so a failed post can ping Slack before anyone notices, and every published post can log itself to your reporting sheet.
What is Zapier?
Zapier is the largest no-code automation platform: you build 'Zaps' that connect a trigger in one app to actions in others, choosing from thousands of integrated services. There's nothing to host and nothing to program — you pick steps in a visual editor and map fields between them.
Nimply's Zapier app exposes the full post lifecycle as Zap steps. Triggers are webhook-powered rather than polled, so they fire the moment a post is published, fails, or is sent for approval. Actions cover creating posts (including platform-specific ones for YouTube, TikTok, Pinterest, and LinkedIn with each platform's real options), uploading media, updating, scheduling, unscheduling, publishing, deleting, and the whole approval workflow. Authentication is a standard OAuth sign-in — you log in to Nimply, pick a workspace, and approve access; no API keys to copy around.
What you can build with Nimply and Zapier
Turn a spreadsheet into a content calendar
Keep your content plan in Google Sheets or Airtable and let a Zap do the publishing: each new row becomes a post, media is imported from the row's file link with Upload Media, and the post is scheduled at the date the row specifies. Editors work in the tool they know; Nimply handles the platforms.
Feed your queue from RSS
Point a Zap at a blog or news feed and have every new item become a post in your next free posting slot. Because Create Post supports the next-slot option, you never have to compute publish times in Zapier — your Nimply posting schedule decides when things go out.
Get alerted before clients notice failures
Platforms reject posts for all kinds of reasons — expired tokens, media specs, policy checks. The Post Failed trigger fires instantly with the error, so a Zap can post it to your team channel or email the account manager while there is still time to fix and reschedule.
Wire approvals into your existing tools
The Approval Requested trigger plus the Approve and Reject actions let you run sign-off wherever your team lives. A draft submitted for review can appear as a Slack message with the content attached, and the approval can flow back to Nimply without anyone opening another dashboard.
Set up Nimply in Zapier
You need a Nimply workspace with at least one social channel connected, and the OWNER or ADMIN role in that workspace to authorize the connection. The Nimply app is currently in Zapier's directory review; until it's listed, the same events are available through Nimply webhooks and Zapier's generic Webhooks by Zapier app.
- 1
Add a Nimply step to your Zap
In the Zap editor, create a new Zap and choose Nimply as the trigger (for example, Post Published) or as an action (for example, Create Post). Search steps also exist — Find Channel by name is handy for routing posts dynamically.
- 2
Sign in and pick a workspace
Click Sign in to Nimply, log in, choose which workspace the Zap should act on, and click Allow access. This is Nimply's standard OAuth consent — the connection is scoped to that one workspace and can be revoked at any time.
- 3
Map your fields
Build the rest of the Zap as usual. File fields from apps like Google Drive, Gmail, or Dropbox work automatically — Zapier passes files as URLs, which Nimply's media upload accepts directly. Platform-specific actions show live dropdowns for things like Pinterest boards and TikTok privacy levels.
- 4
Turn the Zap on
For triggers, this step matters: Zapier registers the webhook with Nimply at the moment the Zap is switched on. You can confirm it worked in Nimply under Settings → Developers, where a 'Zapier' entry appears in the webhook list.
Frequently asked questions
Is the Nimply app already listed in the Zapier directory?
Not yet — the app has been submitted and is going through Zapier's directory review, which typically takes a few weeks. In the meantime you can receive every Nimply event with the generic Webhooks by Zapier app pointed at a Nimply webhook, so nothing is blocked while the review completes.
Which social networks can I post to from Zapier?
All channels connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. YouTube, TikTok, Pinterest, and LinkedIn also have dedicated create actions that expose their platform-specific options, such as Pinterest boards and TikTok privacy levels.
Do the triggers poll, or are they instant?
They are instant. Nimply triggers are webhook-powered, so Post Published, Post Failed, and Approval Requested fire the moment the event happens rather than on a polling interval.
Can a Zap attach images or videos to a post?
Yes. The Upload Media action imports a file from a URL, and Zapier passes file fields from other apps as URLs automatically — so media coming from Drive, Gmail, Dropbox, or a form upload can be attached to a post in the same Zap.
Can I require human review before a Zap publishes anything?
Yes. Create posts as drafts or use the Request Approval action so nothing goes live without sign-off. Combined with the Approval Requested trigger and the Approve and Reject actions, the whole review loop can run through Zapier while Nimply enforces that unapproved posts don't publish.
Why can I not import a ready-made Zap from a JSON file?
Zapier doesn't support importing workflow JSON the way Make and n8n do — Zaps can only be shared as templates from a published app. Once the Nimply app is listed in the directory, templates for the common flows will follow; until then, Zaps are built from the trigger and action list.
Works well alongside
Ready to try it?
Create a free Nimply account, connect your channels, and you're one config entry away.