Zapier
Trigger Zaps on Nimply events and create posts from 6,000+ apps
The Nimply app for Zapier connects your posting queue to everything else you use — no code.
Availability: the app is being submitted to Zapier's public directory; directory review takes a few weeks. If you don't find "Nimply" in the Zap editor yet, check back soon — or use webhooks with Zapier's generic Webhooks by Zapier app in the meantime.
What it does
Triggers (instant, webhook-powered — no polling):
| Trigger | Fires when |
|---|---|
| Post Published | a scheduled post goes live |
| Post Failed | a platform rejects a post — alert your team before the client notices |
| Approval Requested | a draft is sent for sign-off |
Actions: Create Post (draft / next slot / now / at a time, with media), platform-specific creates — Create YouTube Video, Create TikTok Post, Create Pinterest Pin, Create LinkedIn Post — with each platform's full option set (live dropdowns for Pinterest boards and TikTok privacy levels), Upload Media from URL, plus the full post lifecycle — Update, Schedule, Unschedule (back to draft), Publish, Delete, and the approval workflow (Request Approval, Approve, Reject). File fields from other apps (Drive, Gmail, Dropbox…) work automatically — Zapier passes files as URLs, which the upload action accepts directly. Search: Find Channel by name.
Connect
- In the Zap editor, add a Nimply trigger or action and click Sign in to Nimply.
- Log in, choose the workspace, and click Allow access — the standard Nimply OAuth consent.
- Build your Zap as usual.
Zap ideas
- New RSS item → Create Post (next free slot) on all channels.
- Post Failed → Slack message to #marketing with the error.
- New row in Google Sheets → Upload Media → Create Post scheduled at the row's date.
- Post Published → log the post URL to Airtable for client reporting.
Why no copy-paste workflow here?
Unlike n8n and Make, Zapier doesn't support importing workflow JSON — Zaps can only be shared as templates from a published app. Once the Nimply app is listed we'll publish Zap templates for the common flows; until then, build from the trigger/action list above.
Troubleshooting
- Connection fails at consent — you need the OWNER or ADMIN role in the workspace.
- Trigger never fires — the Zap must be turned ON (Zapier registers the webhook at that moment); check Settings → Developers → the webhook list shows a "Zapier: …" entry.