> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/loops.md).

# Loops

Create a Loops API key and connect the Appmixer Loops connector.

The Appmixer Loops connector (**Create Contact**, **Update Contact**, **Find Contact**, **Delete Contact**, **Create Contact Property**, **List Contact Properties**, **List Mailing Lists**, **List Transactional Emails**, **Send Event**, **Send Transactional Email**, **Make API Call**) uses **API key** authentication. You do not need to register an OAuth app with Loops. Each user creates an API key in their Loops account and enters it when they connect Loops in Appmixer.

***

## 1. Create an API key

1. Sign in to [Loops](https://app.loops.so).
2. Open [Settings → API](https://app.loops.so/settings?page=api).
3. Generate a new API key.
4. Copy the key right away. Loops does not show it again, so store it somewhere safe.

{% hint style="info" %}
A Loops API key belongs to one Loops team. Every request made with the key works with that team's audience, mailing lists and transactional emails. Loops has no sandbox, so use a separate team if you want to test flows without touching your production audience. Emails to `@example.com` and `@test.com` addresses are accepted by the API but never delivered.
{% endhint %}

***

## 2. Connect in Appmixer

When you add a Loops component to a flow, Appmixer asks you to connect an account. Paste the key into the **API Key** field.

Appmixer sends the key as a bearer token (`Authorization: Bearer <key>`) to `https://app.loops.so/api`. To check the key, it calls `GET /v1/api-key`. The connection is named after the Loops team the key belongs to.

**Make API Call** only sends requests to `https://app.loops.so`. It rejects other hosts and URLs that contain credentials, so the key is never sent anywhere else.

***

## 3. Prepare transactional emails

**Send Transactional Email** only works with a transactional email that is **published** in Loops, and Loops only lets you publish once your **sending domain is verified**. Before you use the component:

1. Verify your sending domain under **Settings → Domain** in Loops. Add the SPF, DKIM and MX records Loops shows to your DNS, then click **Verify Records**. Free hosting subdomains cannot be used.
2. Create the transactional email under **Transactional**, design it and click **Publish**. A draft that was never published cannot be sent.
3. If the email uses data variables (for example `{data.userName}`), pass a value for each of them in **Data Variables**, or set a fallback in Loops. Missing required variables make the send fail.

**List Transactional Emails** returns drafts as well. A draft has an empty `publishedEmailMessageId`.

***

## Rate limits

Loops allows 10 requests per second per team. Content endpoints (for example `/v1/transactional-emails`) are limited to 60 requests per 60 seconds. The connector queues requests to stay within these limits (10 requests per second, and 60 requests per minute for **List Transactional Emails**) for each Appmixer user.

***

## Troubleshooting

* **401 when connecting:** check that you copied the whole key and that it has not been deleted under **Settings → API**.
* **Make API Call fails with "API Endpoint Path must target <https://app.loops.so>":** use a path such as `/v1/lists` or a full URL on `https://app.loops.so`.
* **404 "No published email message found for this TransactionalEmail" from Send Transactional Email:** the email is still a draft. Publish it in Loops (see [Prepare transactional emails](#3-prepare-transactional-emails)).
* **"Your sending domain is not verified" when publishing in Loops:** finish the domain verification under **Settings → Domain** first.
* **429 errors:** several flows share the same Loops team limit. The connector retries, but very busy flows can still hit the limit.

***

## Backoffice configuration

Configuration ID: `appmixer:loops`. For how to set connector configuration values, see [Connector Configuration](https://docs.appmixer.com/getting-started/services).

You do not need any Backoffice configuration to authenticate, because every user enters their own API key. There are two optional keys:

* `listCacheTTL`: optional. How long, in milliseconds, the lists of mailing lists and transactional emails shown in the Inspector dropdowns are cached. The default is `120000` (2 minutes).
* `outputFilePrefix`: optional. A prefix for the names of CSV files created when **Find Contact**, **List Contact Properties**, **List Mailing Lists** or **List Transactional Emails** runs with the **Store to CSV file** output type. Files are named `<prefix>-<component label in the flow>.csv`. The default is `loops-objects-export`.

```bash
appmixer service-config set appmixer:loops -u -d '{
  "listCacheTTL": 120000,
  "outputFilePrefix": "loops-objects-export"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/loops.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
