Make (formerly Integromat) is the visual end of the automation spectrum: scenarios are drawn as flowcharts, data is mapped between modules by dragging fields, and you can watch each execution step through its bubbles. If your content operation already lives in Make — forms feeding sheets, sheets feeding CRMs — the Nimply app lets the same scenarios feed your social channels.
The module set covers the full lifecycle. Watch Events is an instant trigger that registers a Nimply webhook automatically and fires on post, approval, and channel events. Create a Post picks channels from a live dropdown and supports draft, next free slot, publish now, or a specific time. And where most integrations stop at URL-based media, Nimply also ships an Upload Media (Binary) module, so file data produced by a previous module can go straight into a post without ever being hosted anywhere.
What is Make?
Make is a visual automation platform where workflows are called scenarios: chains of modules that trigger, transform, route, and act on data across hundreds of connected apps. Compared with simpler automation tools it leans toward power users — routers, iterators, and error handlers make genuinely branching logic possible without code.
Nimply's Make app plugs into this with modules rather than raw API calls. Alongside the general Create a Post module there are platform-specific ones — Create a YouTube Video, TikTok Post, Pinterest Pin, and LinkedIn Post — each exposing that platform's real option set: YouTube category, visibility, and license; TikTok privacy levels loaded from the connected account plus disclosure toggles; Pinterest boards with link and alt text; LinkedIn visibility. Updating, scheduling, unscheduling, media uploads, and channel listing round out the set. Connecting is an OAuth flow: you sign in to Nimply from the module, pick a workspace, and allow access.
What you can build with Nimply and Make
Publish an Airtable calendar automatically
A scenario can walk your Airtable content calendar and create each post at the row's publish date using Schedule a Post's exact-time option. Because channels are picked from a live dropdown (or mapped from row data), one scenario can serve every channel in the workspace.
Route failures to the right person
Watch Events fires the instant a post fails, with the error attached. Add a router after it and each account's failures can go to a different owner — an email to the account manager here, a Slack message there — before the gap in the feed becomes visible.
Collect content through forms
A form submission with an attached file becomes a reviewable draft: upload the media, create the post as a draft, and let a human polish and schedule it in Nimply. This is a comfortable pattern for teams where contributors submit ideas but an editor owns the queue.
Handle real binary files, not just links
Modules that generate or transform files — image tools, PDF renderers, HTTP downloads — output binary data. The Upload Media (Binary) module takes that data, name, and MIME type and handles the presigned upload internally, returning a media ID you can attach to the next Create module. No intermediate hosting step required.
Set up Nimply in Make
You need a Nimply workspace with connected channels and the OWNER or ADMIN role to authorize the app. The Nimply app is currently in Make's review process; until it's listed, everything on this page is achievable with Make's generic HTTP and Custom webhook modules using a Nimply API key — the docs include a starter blueprint for exactly that.
- 1
Add a Nimply module to a scenario
Create a scenario and add a Nimply module — Watch Events if you want the scenario to react to Nimply, or one of the Create modules if the scenario should produce posts. Platform-specific modules are worth reaching for when you need the full option set of YouTube, TikTok, Pinterest, or LinkedIn.
- 2
Create the connection
Click Create a connection, log in to Nimply, pick the workspace, and click Allow access. The connection is reused across every Nimply module in your scenarios, and it only ever acts on the one workspace you chose.
- 3
Map data between modules
Wire the rest of the scenario as you normally would. Files from other Make modules usually arrive as URLs, which Upload Media from URL accepts directly; for actual binary output, use Upload Media (Binary) instead. Both return a media ID to attach to a post.
- 4
Test the trigger with sample data
For scenarios starting from Watch Events, click Run once and fire a test delivery from Nimply so Make captures a sample payload — that sample is what you map fields from. The webhook itself is registered automatically when you set the trigger up.
Frequently asked questions
Is the Nimply app available in Make yet?
The app is going through Make's review process. Until it is listed, the same functionality is available today through Make's generic HTTP module with a Nimply API key and the Custom webhook module with Nimply webhooks — the developer docs provide a copyable starter blueprint with the HTTP module pre-configured.
Which events can Watch Events react to?
Post events (published, failed, created, updated, deleted), approval events, and channel events. It is an instant trigger: adding it registers a Nimply webhook automatically, so scenarios fire when the event happens rather than on a schedule.
Which social platforms can a scenario post to?
Everything connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. The dedicated YouTube, TikTok, Pinterest, and LinkedIn modules additionally expose those platforms' specific publishing options.
How do I get files from other modules into a post?
Two ways. If the file arrives as a URL — which is how most Make modules pass files — Upload Media from URL imports it directly. If a module outputs true binary data, Upload Media (Binary) uploads it via a presigned URL; you map the file data, name, and MIME type. Either way you get back a media ID to attach to a post.
Can a scenario schedule posts at exact times, or only publish immediately?
Both, and more: Create a Post supports saving as a draft, dropping into the next free slot of your posting schedule, publishing now, or scheduling at a specific time. Schedule a Post and Unschedule a Post let you set, change, or clear the publish time of existing posts.
Why does my connection fail when I try to authorize?
Authorizing apps requires the OWNER or ADMIN role in the Nimply workspace. If you are an EDITOR or VIEWER, ask a workspace admin to create the connection or grant you the role.
Works well alongside
Ready to try it?
Create a free Nimply account, connect your channels, and you're one config entry away.