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

# Loops

Read contacts, mailing lists, campaigns, and transactional email definitions from your Loops account.

## What It Enables

| Tool                        | Capability | Description                                                                                   |
| --------------------------- | ---------- | --------------------------------------------------------------------------------------------- |
| `find_contact`              | `read`     | Look up a contact by email or userId, including their subscription state and list memberships |
| `list_mailing_lists`        | `read`     | List all mailing lists and their IDs                                                          |
| `list_campaigns`            | `read`     | List campaigns with status, audience target, and scheduling                                   |
| `list_transactional_emails` | `read`     | List transactional email templates and the data variables each expects                        |
| `list_contact_properties`   | `read`     | List all contact property keys, labels, and types                                             |

All tools are read-only. No emails are sent through Notara.

## Setup

**Required:** Loops API key.

**Where to find it:** [loops.so → Settings → API](https://app.loops.so/settings?page=api)

1. In the Notara dashboard, go to **Tools**.
2. Click the **Loops** tile.
3. In the Loops dashboard, go to **Settings → API** and generate a new API key.
4. Paste the key into the credential field and click **Verify & Save**.

Your API key is encrypted at rest with AES-256-GCM.

## Example Prompts

> "Is <user@example.com> subscribed? Which mailing lists are they on?"

> "List all active campaigns and which lists they target."

> "What data variables does the 'welcome' transactional email expect?"