Atlas L6ynztjd84

Stay updated on the status of all your company's support tickets.

Customer portal

Loops integrates with thousands of other platforms so you can sync contacts and trigger emails from around the internet.

Sync customers to your audience and send automated emails.

<Card title="Supabase" icon={  } href="/integrations/supabase"

Send Supabase authentication emails with Loops.


} href="/integrations/auto-bcc"> Sync outgoing mail and contacts to Attio.

<Card title="Bubble" icon={  } href="/integrations/bubble"

Manage contacts and send emails from your Bubble app.


<Card title="Census" icon={  } href="/integrations/census"

Add contacts and contact properties from Census.


<Card title="Clerk" icon={  } href="/integrations/clerk"

Sync users to your audience and send automated emails.


<Card title="Framer" icon={  } href="/integrations/framer"

Add a Loops signup form to your Framer site.


Sync outgoing mail and contacts to HubSpot.

<Card title="Integrately" icon={  } href="/integrations/integrately"

Manage contacts and send emails from over a thousand other platforms.


<Card title="Make" icon={  } href="/integrations/make"

Manage contacts and send emails from thousands of other platforms.


<Card title="Posthog" icon={<div style={{ position: "relative", top: "6px" }}>} href="/integrations/posthog"> Sync users and trigger loops from Posthog.

Sync outgoing mail and contacts to Salesforce.

<Card title="Segment" icon={  } href="/integrations/segment"

Manage contacts and trigger loops from thousands of other platforms.


<Card title="Webflow" icon={  } href="/integrations/webflow"

Add a Loops signup form to your Webflow site.


<Card title="Zapier" icon={  } href="/integrations/zapier"

Send Auth.js magic link emails with Loops.

Import custom MJML email templates from Emailify. Import custom MJML email templates from Email Love.

Overview

Send data to Loops from supported platforms using webhooks.

This feature lets external platforms send webhook events directly to Loops, making it straightforward to create or update contacts in Loops automatically when changes happen in other platforms.

You can also trigger events when webhooks arrive in Loops so you can send automated email after something happens in your other accounts.

First, you create webhook endpoints in your Loops account. These allow other platforms to send data automatically and directly to Loops.

You then create webhooks in the external platforms, which send event data to your Loops endpoint URLs.

Note: we only process webhook events listed below for each provider (and which contain an email address).

We return helpful messages in responses if there is an issue processing a webhook event. Check the webhook logs in your external platforms.

When data arrives in Loops, we grab the email address to create and update contacts in your Loops audience.

For each endpoint you create you can choose to assign a user group value to each new contact, allowing you to create segments from webhook-created contacts.

Any new contact created via a webhook will have a source like "Stripe webhook" so you know where it originated from.

We also support triggering events for each incoming webhook event. This can be useful to automatically send emails when a webhook event arrives in Loops (e.g. a successful payment or a new customer).

To start sending webhook events to Loops, go to your chosen 

A webhook endpoint will be created for you. Copy the endpoint URL and paste it into your external platform.

You may need to copy-paste signing secrets between the platform and Loops for extra security (we will prompt you when this is necessary and give you the steps to do it).

In the endpoint form, you can select the events you want Loops to process, assign a user group, and send a Loops event (which can 

Incoming webhooks

Import emails and contacts to your CRM by adding a BCC address to your marketing emails.

Our Auto BCC feature works with campaigns and loops, but is not offered on transactional emails. By adding a BCC email address in your settings, your emails will be BCCd to this address. Do not use a personal email address, only one generated by your CRM.

Auto BCC is a feature that imports emails and contacts into your CRM platform. This works by adding a BCC email address to all outgoing campaigns and loops emails sent from Loops.

You can add a BCC email address in your 

Be aware that BCCing might not be enough by itself. Some platforms may require you to add the sender email address to an allowlist or for the sender to be a user on your account.

You can record all outgoing email and add contacts into Salesforce using a pre-generated Email to Salesforce address.

You can log all outgoing emails and add new contacts to HubSpot using your pre-generated BCC address.

Make sure to read the "Requirements to log emails to the CRM using the BCC address" section on the page above to make sure the sync works correctly.

 feature, you can sync outgoing emails to your Attio account.

Your Attio log in email has to match the sending email in Loops. For example, if your sending domain is `mail.mydomain.com` and the ["From" address](/sending-first-email#sending-settings) for your email is `bob@mail.mydomain.com`, your Attio account email has to be `bob@mail.mydomain.com` for this integration to work.

Most CRMs have a feature that lets you import email and contacts. Look for a BCC email address and add it to your Loops settings.

Auto BCC

Send Auth0 authentication emails with Loops.

Set up an SMTP connection to send all of your Auth0 emails with Loops.

There are two big benefits to using Loops for sending your Auth0 emails:

You can use [Loops' design editor](/creating-emails/editor) to create (and then easily edit) beautiful transactional emails instead of having to code them with HTML. You get full visibility on which emails are being sent, when, and to whom in your Loops account. Auth0 doesn't offer this view.

In the SMTP Provider Settings section below, enter a value into the "From" field. This value will 

always be overwritten by the values set in your Loops templates

 from the next step, so it can be anything.

The **Send Test Email** button here will not work due to how the Loops SMTP system works. You can test your connection in a later step.

Next, create new transactional emails for the emails you are sending from Auth0. Go to 

. Alternatively, you can select one of our many ready-made templates from the 

 to create nicely-designed templates or make them as simple as you like.

 so you can easily apply consistent branding to all of your emails.

For each Loops template you create, you need to 

, which allow data from Auth0 to be inserted into each email.

 supported in each email from the Auth0 documentation.

Once you're done creating the email and adding the data variables, click 

 button to view the API payload for your template. You will need this for the next step.

Make sure to also publish your email! It won't send unless it's published.

Read our detailed guide for sending transactional emails.

The final step is to make sure your emails in Auth0 are configured to send the correct data to Loops.

Make sure you set up at least the **Verification Email (using Link)** or **Verification Email (using code)** templates in Auth0. Enable other emails based on your user flows.

Loops SMTP integrations work a bit differently than most. Instead of sending a text or HTML email body, you set them up to send API-like data.

, then edit each template to contain the payload as shown in the previous step (you can click the clipboard icon in Loops to copy the full payload).

Make sure that each template you want to use in Auth0 has the **Status** field enabled.

 body, you need to add the Auth0 message variables into the payload. You can do this using double curly brackets like 

Here is an example "Verification Email (using Link)" email template. This payload was copied from the template's Publish page in Loops, then the 

If you want to add each Auth0 user to your Loops audience so you can send marketing email to them, add the 

 flag to your template as below. This will create a contact in Loops using the 

Here's how the template looks in the Auth0 editor:

To test that everything works, click the 

 button beneath the editor. Insert your email address in the modal that appears, then click 

You will also be able to see activity for your email sends in 

The best way to view your Auth0 email history is in Loops. Go to your 

 page then click on one of your emails. Click on 

 in the left menu to view a page containing a table showing all sends and some statistics.

The subject in Auth0 templates is always overwritten by the subject added to the corresponding template in Loops.

The sender email configured in your Auth0 SMTP settings is always overwritten by the "From" address added to your templates in Loops.

Any enabled Auth0 template not set up with the correct API-like payload will fail to send.

Auth0

You must configure a [database adaptor](https://authjs.dev/getting-started/database) to use Magic Link authentication in Auth.js.

There are two big benefits to using Loops for sending your Auth.js emails:

You can use [Loops' design editor](/creating-emails/editor) to create (and then easily edit) beautiful transactional emails instead of having to code them with HTML. You get full visibility on which emails are being sent, when, and to whom in your Loops account. Auth.js doesn't offer this out of the box.

In Loops, create a new transactional email, which will be sent to your users when they attempt to log in.

Here is where you define your email's subject and sending details like From address and Reply to address. (Click the 

 button to reveal all the sending options.)

Then you can creat your email in the editor. We recommend creating a stylish but basic email for magic links, to help with deliverability. Use the 

To add the Auth.js magic link in your email, add a 

. When the email is sent, each user's magic link will be inserted whereever you add the variable.

You can add data variables as URLs to text, buttons and images.

Make sure that your variable is named `url` in the email.

When you're done make sure to Save and Publish your email. Unpublished emails will not be sent.

To use the Loops provider in Auth.js, you'll need to add two environment variables to your project.

The first is an API key. You can generate or copy one from [Settings -> API](https://app.loops.so/settings?page=api).

The second is the ID of your transactional email. Go to the email in Loops and click on to the **Publish** page. Here you will find the **Transactional ID**.

![Publish page with details](https://mintlify.s3.us-west-1.amazonaws.com/loops/images/next.png)

Add both values to your environment, for example in an `.env` file:

```
AUTH_LOOPS_API_KEY=<API_KEY>
AUTH_LOOPS_TRANSACTIONAL_ID=<TRANSACTIONAL_ID>
```


The final step is to configure your project to send emails with the built-in Loops provider.

```javascript auth.js
import NextAuth from "next-auth"
import Loops from "next-auth/providers/loops"
 
export const { handlers, auth, signIn, signOut } = NextAuth({
  adapter: ..., // database adapter of your choosing
  providers: [
    Loops({
      apiKey: process.env.AUTH_LOOPS_API_KEY,
      transactionalId: process.env.AUTH_LOOPS_TRANSACTIONAL_ID,
    }),
  ],
})
```


Don't forget, your email details (subject, from address etc) and content can all be managed from Loops.

 giving you an eye on your sending history.

Auth.js

Integrate the Loops API into your Bubble app with our plugin.

Our Bubble plugin is unfortunately limited to what it can do because of how Bubble works. If you want more flexibility—for example, syncing more contact data to Loops—check out our [tutorial for using Bubble's API Connector](/guides/bubble-api-connector).

 and select your app from the "Install in an application..." dropdown.

Alternatively, go to the Plugins page in your Bubble admin, click "Add plugins" in the top right, and search for "Loops".

To use the plugin you will need to add a Loops API key into Bubble.

 and copy an API key. You may need to create a key first.

Then go to the the Plugins page in Bubble, select the Loops plugin and paste your API key into the "API key" field, prepended with the word "Bearer" and a space.

To use the plugin actions in a workflow, select "Plugins" in the menu and you will see the options show up (prefaced with "Loops - ").

Here's a simple example of using the Bubble plugin to add all new users to your Loops audience.

After your sign up action, add a new "Loops - Create a contact" action.

In the form, add your user email into the "Email" field and user ID into the "User ID" field.

The plugin contains actions that replicate what's possible with the 

 action will create new contacts in Loops using the email address and user ID that you send from Bubble.

If you want to "create or update" users, use the 

You need to provide both email and user ID values, otherwise the underlying API request from Bubble will fail.

 action lets you also send a first and last name to Loops.

 action will find a Loops contact based on the provided email address. This can be used to see if one of your user already exists in your Loops audience.

 action will find a contact by their ID.

This action will update the email address of a Loops contact who has the provided user ID.

This action can also be used to "update or create" contacts. If a contact doesn't already exist with the provided email or user ID, a contact will be created.

This is useful for when a user closes their account in your application and therefore you no longer want to email them from Loops.

 from your application. For example, you may have a welcome loop which sends an email drip campaign to new users.

For the Send an event action, you need to provide an "Event name" value and the user's ID or email address.

Transactional emails are one-time emails like password resets sent by apps to users based on an action.

To send transactional emails, you will first need to 

Once you have written the email and added data variables, you can click 

 to see the example payload for the API.

 (which you added in the email) because you need these in Bubble.

Once you create the action in Bubble, you will see the three fields in the form.

Here is an example API payload for the Loops API:

{ "transactionalId": "clomzp89u635xl30px7wrl0ri",
  "email": "name@email.com",
  "dataVariables": {
    "lastLoggedIn": "20240214T10:01:29Z",
    "plan": "Pro",
  }
}


To get the same effect in Bubble, we need to enter the following into the "Data variables" field:

"lastLoggedIn": "20240214T10:01:29Z", "plan": "Pro"

To add user data into this field, place your cursor and select 

Bubble

Enable sign ups to Loops using a native Carrd form.

 and paste in your form endpoint from the 

Paste the form endpoint you copied from into the 

Our form submission endpoint has rate limiting, so you will see an error in testing if you submit more than once per minute or submit the same email twice.

In addition to collecting the email address, you can also collect any other contact property you want.

Assign the field an "ID" matching the Loops API property name that you want to set. You can check the full list of your available properties from your 

For example, if you want to set the User Group property, you would add a hidden field and set the ID to 

 can be a single mailing list ID or if you want to add subscribers to multiple lists, a comma-separated list of IDs.

Carrd

Send user data from your data warehouse to Loops.

Trigger loops when contacts are created or updated

Loops is a partnered destination for Census. We support syncing data via 

New contacts cannot be created if no email is provided.

You will be prompted to enter your Loops API Token, which you can find on your 

, and to decide if you want to trigger loops when contacts are created or updated.

Loops will now be available as a destination in Census.

When choosing a sync behavior, you can choose either 

Census

Sync contacts and send emails triggered by events in Clerk.

Our Clerk integration is built on top of our 

 feature. This system lets you send webhooks from supported platforms directly to Loops so you can easily sync users and customers as well as send automated emails.

Please read our guide about incoming webhooks

With Clerk, you can keep your user data synced to Loops so you can easily send emails to your userbase.

 event, we sync the following Clerk data to your Loops contacts:

We use the IDs of Clerk users to match contacts in your Loops audience. If the user ID is not found in Loops, we will create a new contact.

There is no user ID available for waitlist events. When a user graduates from your waitlist to being a user (i.e. you accept them and they complete their account), their user ID will be added to your contact in Loops.

If you send other events, they will be ignored.

If you would like to see more events supported, please let us know by sending an email to [help@loops.so](mailto:help@loops.so). Please keep in mind only events that contain an email address are able to be processed.

 to create a new webhook endpoint, which will allow you to send webhook events directly to Loops.

Next, you need to set up webhooks in Clerk.

. Paste in the endpoint URL from Loops, then select the event(s) you want to send (see our 

The last step is to copy the signing secret into Loops. On the webhook page in Clerk, click the eye icon on the right to show the secret in the page. Copy the secret and paste it into the 

Clerk offers a nice way to test webhooks. Click through to the webhook you created and then the 

 dropdown, tweak the example data that's shown, then click 

This will send real data to your Loops account.

You can also test your webhook by creating and editing users in the 

 page in Clerk, or by signing up in your application.

You can see all sent webhooks by going to 

, clicking on the webhook and scrolling down to the 

On Loops' end, you will see new contacts appear in your 

Here are some examples of how you can send data from Stripe to Loops to sync contacts and trigger useful emails to your customers.

Create or update contacts in your Loops audience when a user is created or updated in Clerk.

Create a new Clerk webhook endpoint in Loops (

 events and paste in your endpoint's URL.

 are toggled on on the Clerk settings page.

Create or update contacts in your Loops audience when someone joins your waitlist in Clerk.

 event and paste in your endpoint's URL.

 is toggled on on the Clerk settings page.

To keep track of waitlist users you can use the 

Integrations

Integrations articles

Overview

Incoming webhooks

Auto BCC

Auth0

Auth.js

Bubble

Carrd

Census

Clerk

Framer

Integrately

Novu

Make

Posthog

Segment

Stripe

Supabase

Webflow

Zapier