Permut Zapier integrationAutomate Permut with Zapier.
Permut Zapier integration: 0 triggers, 1 action, 0 searches. Your Zap (the automation you build) starts in another app, then pushes the customer into a live Permut campaign. Three fields are required, and the phone number has to be in international format.
Verified Trustpilot reviews · AI, automation & growth agency
What the Permut Zapier integration actually does for you
Permut runs customer feedback and engagement campaigns, with AI-driven analysis behind them. On Zapier it offers one thing: Send Customer to Campaign. A Zap picks up a customer in another tool and enrolls that person into an active Permut campaign, with a name, a phone number and the campaign to join.
Three outcomes, all from that one action. A buyer who gets the post-purchase campaign: a new order in your shop sends the customer into the right Permut campaign without anyone exporting a list. A form respondent who enters a follow-up sequence: a sign-up form feeds Send Customer to Campaign, and the follow-up starts on the Permut side. A closed deal that triggers a feedback request: when a deal moves in your CRM, the customer joins the campaign that asks how it went.
Now the part the app page leaves out. Permut has no trigger and no search on Zapier. Nothing that happens inside Permut can start a Zap, so feedback collected there will not flow back to your other tools through this integration. A Zap cannot look up a customer in Permut either, or check whether that person is already in a campaign.
So the integration is an entry door, not a two-way bridge. If you are comparing how other tools handle this kind of flow, the Zapier review and the n8n vs Zapier comparison are the places to start.
Zapier vocabulary in one minute
Seven words you will meet in the editor, in plain terms.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Permut has none, so your trigger always comes from another app, like a form or a shop.
- Action
- What the Zap does once it has started. Here, it is Send Customer to Campaign, the only Permut step available.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Each customer sent to Permut is one task.
- Polling vs instant
- Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself the moment it happens. Your trigger app decides which.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What a Permut Zap really costs
Every customer that Send Customer to Campaign enrolls successfully costs one task. The trigger in the other app costs nothing.
- Trigger (other app)0 tasks
- Each customer sent1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
A failed send is not counted. Permut is not a premium app, so it runs on the free plan: 100 tasks a month and Zaps of two steps, one trigger and one action. Add a filter to keep incomplete records out, and the Zap becomes multi-step, which needs a paid plan. How fast it runs depends on your trigger app: if that trigger is polling, the grid below applies.
One more point: in a Zap with several actions, each successful action is counted on its own, so any step you add after Permut raises the bill.
Connect Permut to Zapier in three steps
- 01
Open your Zapier apps
Go to the Apps page of your Zapier account and click + Add connection. A connection is your Permut account linked to Zapier once, then reused by every Zap step that needs it.
- 02
Find Permut
Type Permut in the search box of the dialog, pick it, then click Add connection. You need an existing Permut account, with access to the campaigns you want the Zap to fill.
- 03
Sign in and grant access
A new tab opens on Permut. Sign in with the account that owns your campaigns, then grant Zapier access. The connection shows up in your apps list, ready to use.
Your first Permut Zap
GoalEach new shop order with a phone number sends the buyer into the Permut post-purchase campaign.
- 01
Pick the trigger
In the editor, choose your shop app as the one that starts the Zap, and the new order as the event. Test it: Zapier brings back the three most recent items so you work on a real order.
- 02
Add a filter
Add a filter so only orders with a phone number go through, since Permut requires one. This makes the Zap multi-step, so it needs a paid plan; on the free plan, skip it.
- 03
Add the Permut action
Add Permut, choose Send Customer to Campaign, and type the campaign slug. Map the customer name and the phone number from the order, in international format.
- 04
Test the action
Run the step once and read what came back. Check in Permut that the test customer really entered the campaign before going further.
- 05
Publish
Publish the Zap to switch it on. From then on, each new qualifying order sends one customer to Permut, and each successful send counts as one task.
The Permut action
Permut gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Send Customer to Campaign
ActionIn Zapier“Sends a customer to an active campaign pipeline with contextual event data.”
This action enrolls a customer into an active Permut campaign, along with context from the step that started the Zap. You give it three things: the campaign slug, the customer's full name, and the phone number.
When a Permut Zap breaks
Zapier attaches no help article to Permut, and no limit specific to the app is documented. The failures below come from the action's required fields and from Zapier's general limits.
Read each case before you publish. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.
A required field is empty
Campaign slug, customer name and phone are all required. When the trigger app leaves one of them blank, the send cannot go through for that customer.The phone is in the wrong format
Permut expects the phone number in international format. A local number typed into a form needs reformatting before it reaches the action.Past customers never arrive
A Zap only reacts to what happens after it is switched on. Customers who already existed are not sent; enrolling them is a separate job.A big batch stalls
When the trigger app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.
Need help automating Permut with Zapier?
A person reads every message.



