Pneumatic Make integrationAutomate Pneumatic with Make.
Can a finished Pneumatic workflow kick off the next step on its own? The Pneumatic Make integration gives you 8 modules: 4 triggers and 4 actions. This guide is for ops people who run Pneumatic and want to wire it to other tools without writing code.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Pneumatic Make integration automate?
The Pneumatic Make integration links your Pneumatic account to Make, a visual tool where you build a scenario (the automation itself) out of modules, one brick per step. Make can notice when workflows start or finish and when tasks are completed or returned, then launch new workflows from your templates.
Start a process from another tool. A new signed contract, a form entry or a row in a sheet can feed Launch a Workflow Based on a Specific Template, so the onboarding checklist opens in Pneumatic without anyone clicking Start.
Tell people when a task comes back. Watch Task Returned spots tasks sent back for rework, and the next module can post a message in the chat tool your team already reads.
Keep a record of finished processes. Watch Workflow Completed picks up each closed workflow, and Make can write a line per run into a spreadsheet or a CRM for reporting.
Know the limits before you build. Make itself warns that its Pneumatic documentation is incomplete, because little public information exists about the app. The module names are clear, but field details are not documented, so test each module with Run once. When a listed module is missing, Make an API Call reaches the Pneumatic API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.
How do you connect Pneumatic to Make?
- 01
Open the connection window
Add any Pneumatic module to your scenario and click Create a connection. A connection is your Pneumatic account linked to Make once, then reused by every Pneumatic module you add later.
- 02
Name it so you can find it again
Giving the connection a name is optional, but it helps once you manage several accounts. Something like the workspace name is enough to pick the right one from the list later.
- 03
Authorize and save
Make either sends you to a Pneumatic page to approve access or asks for the key Pneumatic gives you. Complete that step, then click Save and the module is ready to use.
Build your first scenario with Pneumatic
GoalWhen a new request lands in another app, Make launches a Pneumatic workflow from the template you pick.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. The first module is the one that notices new requests, for example a form or a sheet you already use.
- 02
Add the Pneumatic action
Click the + on the right of that first module, search for Pneumatic and pick Launch a Workflow Based on a Specific Template. Click Create a connection if this is your first Pneumatic module.
- 03
Choose the template and map data
Fill in the module fields. Once the connection exists, Make can list what it reads from your account. Map values from the first module, such as a client name, into the fields Pneumatic shows.
- 04
Test with Run once
Create one test request, then click Run once. Make runs the scenario a single time and shows the bundles each module received. Check in Pneumatic that the workflow started with the right data.
- 05
Schedule and switch it on
Open the clock on the first module to set how often Make checks for new requests. A new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.
Which Pneumatic triggers can start a scenario?
4 modules start a scenario when something happens in Pneumatic. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pneumatic as soon as it happens.
Watch Task Completed
triggerIn the docs onlyGet a new bundle every time someone ticks off a task in Pneumatic, so the step after it can happen outside the app. A bundle is one item passed from module to module, here one completed task.
Watch Task Returned
triggerIn the docs onlyCatch the tasks that were sent back instead of approved, so rework never sits unseen in a queue. This trigger is the one for exceptions, while Watch Task Completed follows the happy path.
Watch Workflow Completed
triggerIn the docs onlyKnow the moment a whole process is closed, not just one step of it. Each finished workflow arrives as one bundle that later modules can archive, report on or pass to another app.
Watch Workflow Started
triggerIn the docs onlyHear about new processes as soon as Make next looks, whether a person launched them by hand or another scenario did. That lets outside tools prepare before the first task is even touched.
What can Make do in Pneumatic?
Pneumatic gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Get Template Details
ActionIn the docs onlyGoing by its name, it reads what a Pneumatic template contains so the next modules can use it, which is handy before launching anything from that template.
Launch a Workflow Based on a Specific Template
ActionIn the docs onlyStart a fresh Pneumatic workflow from one of your templates without opening the app. This is the module that turns an event elsewhere into a running process.
Make an API Call
ActionIn the docs onlyReach any endpoint of the Pneumatic API from your scenario, reusing the same connection instead of setting up keys again. It covers what the other seven modules leave out.
Stop Watching an Event
ActionIn the docs onlyIts name points to a cleanup job: telling Pneumatic to stop following an event it was watching for Make. Make gives no further description of this module.
Need help automating Pneumatic with Make?
A person reads every message.
