Loopify Zapier integrationAutomate Loopify with Zapier.
Loopify Zapier integration: 1 trigger, 3 actions, 0 searches. A Connect block in a Loopify flow can start an automation the moment a contact reaches it, and three actions push contacts the other way, into Loopify and into its flows.
Verified Trustpilot reviews · AI, automation & growth agency
What the Loopify Zapier integration is for
The Loopify Zapier integration links Loopify, a marketing automation tool built around flows, to the other apps you use. In one direction, a contact passing a Connect block in a flow sends its data out. In the other, a contact created elsewhere gets added or updated in Loopify, or dropped into a flow at the right entry point.
Three results come out of it. A flow that reports back: Flow Webhook fires each time a contact reaches a Connect block, so a list, a sheet or another tool learns which contacts went through that branch. A contact base that stays current: Create/Update a Contact writes a contact into Loopify, or refreshes the one already there. Flows that start from outside: Add Contact to New Entry and Add to API Entry place a contact at the entry block of a flow, so the sequence you built in Loopify starts for them.
What Zapier does not do with Loopify matters as much. There is no search: a Zap cannot look up a Loopify contact by email to find its ID. And the only event Loopify reports is a contact reaching a Connect block. To follow another moment of the journey, the flow itself has to hold a Connect block at that point.
The same app is covered for another tool on the Loopify Make integration page, and the criteria that separate the two platforms are laid out in Make vs Zapier.
Zapier words, in plain English
Eight words carry the rest of this page. Here is what each one means when you sit in front of the editor.
- 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. Once the Zap is on, Zapier waits for it. Loopify offers one: Flow Webhook.
- Action
- What the Zap does once it has started: the step that writes or sends something for you, like adding a contact to a flow.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. Flow Webhook works this way.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Loopify has none of these.
- 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 Loopify Zap really costs
Loopify is not a premium app, so it runs on the free plan. Zapier bills in tasks, and only actions that succeed count.
- Flow Webhook trigger0 task
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
Flow Webhook costs nothing, however many contacts reach the Connect block. Each action that goes through costs one task, whether it writes into Loopify or into another app, and a failed action is not counted. The free plan gives 100 tasks a month and Zaps of two steps: one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below is Zapier's standard one for polling triggers; it does not apply to Flow Webhook, which is instant.
Connect Loopify to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need a Loopify account first, with write access to any flow or contact list you do not own yourself.
- 02
Pick Loopify
Type Loopify in the search box of the dialog that opens, pick it from the list of results, then click Add connection. A new tab opens on the Loopify side.
- 03
Sign in and grant access
Sign in to Loopify in that tab and grant Zapier access to the account. The connection then appears in Apps and every Loopify step of every Zap reuses it.
Your first Zap: log the contacts that reach a Connect block
GoalEvery contact that reaches a Connect block in your flow, and passes the filter you set, becomes a new row in your spreadsheet.
- 01
Prepare the flow in Loopify
Add a Connect block set to use webhooks, activate the flow, and pass one test contact through it. A New-Entry block in the flow is a handy way to send a contact in on demand.
- 02
Set the trigger
Build the Zap from Loopify and Flow Webhook, then choose the Flow and the Connect Block. Run the test: Zapier brings back the three most recent contacts that went through.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value. The Zap is now multi-step, so it needs a paid plan.
- 04
Add the spreadsheet row
Pick your spreadsheet and its add-row action, then map the contact fields from the trigger into the columns. Test the step and check the row it wrote.
- 05
Publish
Click Publish. From then on, each contact that reaches the Connect block and passes the filter gets its row, straight away and whatever the plan.
The Loopify trigger
1 event starts a Zap when something happens in Loopify, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Flow Webhook
Instant triggerIn Zapier“Triggers when a Connect block occurs in Flow.”
Starts your Zap each time a contact reaches a Connect block in one of your Loopify flows, and hands over that contact's data to the next steps. You choose the flow and the exact Connect block in the trigger settings, so one Zap listens to one point of one flow.
The 3 Loopify actions
Loopify gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Contact to New Entry
ActionIn Zapier“Adds a contact to a "New Entry" block in Flow”
Places an existing Loopify contact at the New Entry block of a flow, so the flow starts for that person.
Add to API Entry
ActionIn Zapier“Adds a contact to an "API Entry" block in Flow”
Sends a contact into a flow through its API Entry block, the entry point built for other systems.
API Entry block and you want Zapier to feed it from a form or a list.API Entry Block are required, so the block has to exist in the flow before you set up the step.Create/Update a Contact
ActionIn Zapier“Create or update a contact”
Writes a contact into Loopify: a new one if it is not there yet, or a refresh of the existing one.
When a Loopify Zap breaks
Zapier ties no help article to Loopify and documents no rate limit for it. What breaks comes from Zapier's own rules and from the setup the fields require.
Four cases come back most often. For a Zap that stops for a reason not listed here, the Zapier troubleshooting page goes further.
The trigger test finds nothing
Flow Webhook only finds data once the flow is active and at least one test contact has passed the Connect block. A New-Entry block lets you send one in.Contacts from before never arrive
A Zap only reacts to what happens after you publish it. Contacts that passed the Connect block earlier are not picked up and need a separate one-off export.The flow feeds itself
If the Zap sends a contact back into the same flow that holds its Connect block, each pass sets it off again and burns through tasks fast.A big batch is held back
After a bulk import pushes many contacts through the Connect block at once, Zapier's flood protection can hold the batch back.
Need help automating Loopify with Zapier?
A person reads every message.
