Our Zapier integration lets you:
- Create, find and update contacts
- Send events to trigger loops
- Send transactional email
- Trigger Zaps based on activity in your Loops account
Creating a new Zap
To create a new Zap—for example, to connect Tally and Loops—you can either type out what you want to create.

Authentication
To be able to use Loops Actions, you need to connect to your Loops account. From the Account tab, click Sign in.

You can create connections to multiple Loops accounts from a single Zapier account.
Triggers
There are a number of Loops triggers available in Zapier:- Contact created
- Contact unsubscribed
- Contact deleted
- Contact subscribed to mailing list
- Contact unsubscribed from mailing list
- Campaign email sent
- Loops email sent
- Transactional email sent
The “Email sent” triggers will fire for every individual email sent. If you send a campaign to 1,000 contacts, it will be triggered 1,000 times.
contactIdentity
object to identify the contact that triggered each event.
For example, the “Contact subscribed to mailing list” trigger will fire when a contact is subscribed to a mailing list and contains the following data:
Actions
Add a contact
This action adds new contacts to your Loops audience. If the email address already exists, it will return an error. All default contact properties are available, plus mailing lists and any custom contact properties added to your Loops account. Only the Email field is required. The Source field defaults to “Zapier” but you can update this to whatever value you like.
Update a contact
The “Update a contact” action will create a contact if a matching contact does not already exist, making it useful if you don’t know in advance if a contact exists in Loops.

Find a contact
This action supports searching your contact list for a specific email address. You also have the option to create a new user if one is not found.
Delete a contact
This action will delete a contact by email address.
Send an event
This event will send an event in Loops. You need to specify an Email or User ID value to identify the contact, plus an Event Name. The action also supports event properties and mailing lists. The Email/User ID and Event Name fields are required.
Send a transactional email
This action sends a transactional email and can optionally add a contact to your audience. The Transactional Id, Email and Data Variables fields are required.