Resources · Zapier integration

Loops Zapier integrationAutomate Loops with Zapier.

The Loops Zapier integration gives you 8 triggers, 5 actions and 1 search to move contacts, events and transactional emails between Loops and the rest of your tools. Every trigger is instant, and Loops works on the free plan.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loops Zapier integration actually does for you

The Loops Zapier integration links your Loops audience to the other apps you use, without anyone copying addresses by hand. Something happens on one side, a contact is created, an email goes out, someone unsubscribes, and Zapier carries the consequence to the other side. On the Loops side, marketing and transactional email for software businesses; on the Zapier side, the glue that ties it to everything else.

Three results people build first. A sign-up form that feeds your audience: each new submission becomes a contact through Add Contact, so nobody exports a file at the end of the week. An opt-out log: Contact Unsubscribed writes every person who leaves your audience into a spreadsheet anyone on the team can open. A signal from elsewhere: Send Event pushes something that happened in another tool into Loops under a name you choose.

What Zapier does not do here matters just as much. There is no action that sends a campaign or builds a mailing list: those stay inside Loops. There is no trigger on opens or clicks either, only on emails being sent and on contacts changing. And since all eight triggers are instant, the free-plan wait between checks never comes into play on this app (a rare comfort).

If you are weighing platforms, the Loops Make integration and the Zapier review are the two pages to open next.

Vocabulary

Zapier words, in one minute

Seven words come back on every line of this page. Here is what they mean in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a Loops Zap really costs

Loops is not a premium app, so it runs on the free plan. The trigger never costs a task, and watching for new data is free however often it happens.

  • Free plan100 tasks a month, unlimited Zaps
  • Zap size on FreeTwo steps: one trigger, one action
  • Premium appNo, Loops works on every plan
  • Loops triggers8 instant, 0 polling

Each action that goes through counts as one task; one that fails is not counted. A Zap with three actions eats three times more than a Zap with one. The free plan stops at two steps, so adding a filter, a search or a second action makes a multi-step Zap, which needs a paid plan. The interval grid below is the general Zapier rule for polling triggers: it does not apply to the instant triggers of Loops.

Connect

Connect your Loops account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your Loops account linked once, then reused by every step that touches Loops.

  2. 02

    Pick Loops

    Type Loops in the search box of the dialog, select it, then click Add connection. You need an existing Loops account, plus access to anything you do not own yourself and want the Zap to change.

  3. 03

    Sign in and allow access

    A new tab opens on Loops. Sign in, then grant Zapier access to the account. Back in Zapier, the connection appears in your list and every Loops step can pick it.

First Zap

Your first Zap: an opt-out log for Loops

GoalEach time someone leaves your Loops audience, look the contact up and write one row in a shared spreadsheet, so the opt-out is visible outside Loops too.

  1. 01

    Build the trigger

    Create a Zap, pick Loops and the Contact Unsubscribed event, then choose your Loops connection. It is instant, so nothing waits for a timer.

  2. 02

    Test it on a real contact

    Click test: Zapier brings back the three most recent unsubscribes from your account. Pick one, so every later field is mapped on real data, not a blank example.

  3. 03

    Look the contact up

    Add a Loops step with Find Contact and map the email from the trigger into Contact Email. The search hands the contact's properties to the next step.

  4. 04

    Write the row

    Add your spreadsheet tool with its create-row action and map the email and the properties you care about into its columns. One row per person who left.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the row looks right, click Publish. With a search step in the middle, this Zap needs a paid plan.

Triggers

Loops triggers: what starts a Zap

8 events start a Zap when something happens in Loops, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Campaign Email Sent

Instant trigger

In Zapier“Triggers when a campaign email is sent to a recipient (warning: will trigger for every recipient of your campaign).”

Each time a Loops campaign email reaches a recipient, this trigger hands Zapier that person and that send. It works person by person, not campaign by campaign.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a record of who received a given campaign, one row per recipient in a spreadsheet.
Watch out
a campaign sent to a large audience starts the Zap once per recipient, and every action behind it is a task each time.
2

Contact Subscribed to Mailing List

Instant trigger

In Zapier“Triggers when a contact is subscribed to a mailing list.”

The moment a contact joins one of your Loops mailing lists, this trigger starts the Zap with that contact and that list. Your audience already exists; this is about the lists inside it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a person opts into a specific list and you want that same choice copied into another tool.
Watch out
if you only care about one list, add a filter on the list name, which turns the Zap into a paid-plan Zap.
3

Contact Unsubscribed From Mailing List

Instant trigger

In Zapier“Triggers when a contact is unsubscribed from a mailing list.”

Somebody leaves a single mailing list but stays in your audience: that is the event caught here. It is narrower than a full unsubscribe, and the two should not be confused.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a contact drops out of one topic list and you want the matching preference updated wherever else you keep it.
Watch out
a person who unsubscribes from your whole audience is a different event, handled by Contact Unsubscribed.
4

Contact Unsubscribed

Instant trigger

In Zapier“Triggers when a contact is unsubscribed from your audience in Loops.”

This one fires when a person leaves your Loops audience altogether, not just one list. It is the strongest opt-out signal Loops gives Zapier, so it deserves care.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a list of opted-out addresses in another tool and want every new opt-out copied there.
Watch out
never pair it with an action that subscribes the same contact back, or the Zap undoes the person's choice.
5

Contact Created

Instant trigger

In Zapier“Triggers when a contact is created in Loops.”

A new contact appears in your Loops audience, and this trigger hands it to the next step. It is the plainest way to keep another tool in step with who joins.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new contact should also exist in another tool that keeps a list of the same people.
Watch out
a bulk import creates contacts in a burst, and each one starts the Zap and spends tasks.
6

Contact Deleted

Instant trigger

In Zapier“Triggers when a contact is deleted in Loops.”

When a contact is removed from Loops for good, Zapier hears about it here. Unlike an unsubscribe, the person is gone from your audience, not just opted out.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a contact removed from Loops should also be removed from another tool that stores the same email address.
Watch out
by the time the Zap runs the contact no longer exists in Loops, so a later Find Contact step finds nothing.
7

Workflow Email Sent

Instant trigger

In Zapier“Triggers when a workflow email is sent to a recipient (warning: will trigger for every recipient of your workflow's emails).”

Loops calls its automated sequences workflows. Every email one of them sends to a recipient starts the Zap, once for that person and that email.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want each email a workflow sends logged in another tool, so anyone can see what a contact already received.
Watch out
it fires for every recipient of every workflow email, so a busy workflow can drain a free plan fast.
8

Transactional Email Sent

Instant trigger

In Zapier“Triggers when a transactional email is sent to a recipient.”

Whenever Loops sends a transactional email to someone, this trigger starts the Zap with that send.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an audit trail of every transactional message, kept in a spreadsheet outside Loops.
Watch out
if a Zap sends these emails through Send Transactional Email, this trigger fires again for each one; keep the two Zaps apart.
Actions

Loops actions: what the Zap does

Loops gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Contact

Action

In Zapier“Adds a contact to your audience.”

Puts a new person into your Loops audience from any app that has an email address. Email is the only field it requires.

When to use it
a form in another tool collects an address and you want it in Loops straight away.
Watch out
new contacts come in subscribed by default, so only touch the Subscribed field if you mean to change that.
2

Delete Contact

Action

In Zapier“Deletes a contact from your audience.”

Removes a contact from your Loops audience, using the email address as its only required input.

When to use it
a person removed from another tool should leave your Loops audience without anyone doing it by hand.
Watch out
deletion is not an unsubscribe. If the person should only stop receiving email, Update Contact with the Subscribed field is the gentler route.
3

Send Event

Action

In Zapier“Sends an event to Loops.”

Tells Loops that something happened, under an Event Name you choose, which is the field it cannot do without.

When to use it
something happens in another tool and you want Loops to receive it as an event.
Watch out
Event Name is the one field you cannot skip, and the Zap sends exactly what you type, so check the spelling before you publish.
4

Send Transactional Email

Action

In Zapier“Sends a transactional email.”

Sends one of your Loops transactional emails to an address you choose. It needs the Transactional Id of that email and the recipient's Email.

When to use it
a new row or a new entry in another tool should send one specific person one specific email.
Watch out
the Add contact to your audience option creates a contact when none matches; switch it on only if you want that.
5

Update Contact

Action

In Zapier“Updates the properties of a contact in your audience.”

Changes the properties of a contact already in your audience, found by its email address, which is required.

When to use it
a value that changes in another tool should be reflected on the matching Loops contact.
Watch out
the Subscribed field can flip someone's status, so leave it empty unless that is the point of the Zap.
Searches

The Loops search: finding a contact first

1 search step looks for data that already exists in Loops, so a later step can use it.

A search step looks up a contact that already exists so later steps can use it. In the editor, it sits at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not the one you hoped for.

1

Find Contact

SearchFind or create

In Zapier“Finds a contact in your audience by email.”

Looks up a contact in your Loops audience from a Contact Email, the one field you must fill. What it returns feeds the next steps.

When to use it
before updating someone, check that they are already in Loops and read their current properties.
Watch out
the editor also lists Find or Create Contact; it is this same search with the create box ticked, not a separate operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nobody stops the Zap there and skips the steps that relied on it. Switched on, the Zap continues with nothing in hand.
  2. Create Contact if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing contact.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass every match along at once.
When it breaks

When a Loops Zap breaks

Zapier attaches no help article to Loops, so the traps below come from how Zapier itself behaves, applied to what Loops sends.

None of them shows up while you build. They appear once the Zap is live and a real campaign, import or workflow runs through it. If you are already stuck, the Zapier troubleshooting page is the next stop.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Contacts created last month are not picked up; moving that backlog is a separate job.

  • One campaign, hundreds of runs

    Campaign Email Sent and Workflow Email Sent start the Zap once per recipient. Each run spends one task per successful action, which empties a free plan quickly.

  • The Zap that feeds itself

    Contact Created plus Add Contact on the same audience, or Transactional Email Sent plus Send Transactional Email: the Zap writes where its trigger watches and sets itself off again.

  • Bulk import held back

    A large import into Loops can send Zapier a sudden wave of new contacts. Zapier's flood protection may hold that batch back instead of running it all.
Need help

Need help automating Loops with Zapier?

A person reads every message.

FAQ

Loops Zapier integration: frequent questions

01Is the Loops Zapier integration free?
Yes, as long as you stay within the free plan's limits. Loops is not a premium app, so Zapier does not reserve it for paid plans. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap is limited to two steps: one trigger and one action. The moment you add a filter, a search such as Find Contact or a second Loops action, the Zap becomes multi-step and you need a paid plan. Plenty of useful Loops Zaps fit in two steps, such as Contact Unsubscribed writing one row in a spreadsheet.
02How many tasks does a Loops Zap use?
One task per action that completes, nothing for the trigger. A Zap that runs Contact Created then one action costs one task per new contact. The catch on Loops is the sending triggers: Campaign Email Sent and Workflow Email Sent fire for every single recipient. A campaign to a large list therefore runs the Zap once per person, and each run costs a task per successful action behind it. Actions that fail are not counted. Check the size of your sends before pointing them at a Zap on the free plan's 100 tasks.
03Do Loops triggers run in real time?
Yes, all eight of them. Every Loops trigger is instant: Loops itself tells Zapier the moment a contact is created, deleted or unsubscribed, or an email is sent, and the Zap starts right away. The interval grid that slows polling triggers on the free plan, 15 minutes between checks, does not apply here. That makes Loops one of the comfortable apps on a free account. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is an easy way to confirm it.
04What does it take to connect Loops to Zapier?
An existing Loops account and a Zapier account. From the Apps page of Zapier, click + Add connection, search for Loops, then sign in to Loops in the tab that opens and grant Zapier access. The connection is saved once and every Loops step reuses it. If the Zap will touch things you do not own yourself in Loops, your account needs read or write access to them. For Send Transactional Email, the transactional email must already exist in Loops, since the action asks for its ID.
05Why does a Loops Zap run once for every person in a campaign?
Because Campaign Email Sent is built that way: it fires per recipient, not per campaign. Loops reports each delivery separately, so a send to a whole audience reaches Zapier as one event per person. If what you actually want is a single note that a campaign went out, this trigger is the wrong tool, and Zapier offers no Loops trigger at campaign level. If you keep it, make sure the action behind it is worth one task per recipient, and test with a small list first.
06What if the Loops action you need is not in the list?
Then this integration cannot do it, because the editor offers nothing beyond the 5 actions and 1 search described above. Two gaps come up most: there is no action to send a campaign and none to create a mailing list, so both stay in Loops. Triggers have their own blind spot, since none reacts to opens or clicks. When a step is missing, the work is done in Loops by hand, or on another automation platform, once you have checked that its Loops operations really include that step.
07Zapier, Make or n8n for Loops?
It depends on three criteria rather than on a winner. First, the operations: compare the list on this page with what each platform exposes for Loops, and pick the one that has the trigger and the action your scenario needs. Second, volume: on Zapier each successful action is a task, so per-recipient triggers on big sends weigh on the bill. Third, who maintains it: a teammate who never automated anything will find a two-step Zap the easiest to read.
Same platform

Other docs you might need on this stack.

Browse all integrations