AI agent for Loops: campaign reports, transactional emails, contacts and workflows
Loops connects with one API key (Loops → Settings → API); the key belongs to one Loops team, which becomes one connection. The agent has 14 reads and 6 writes. Property updates follow your approval setting; sending email, adding or subscribing a contact and deleting one always wait for a person. Contacts are masked in every read.
Connecting Loops
- 1In Loops open Settings → API and generate an API key.
- 2Open Integrations → the Loops card, paste the key and press Check and save. Agent Planners checks it with Loops before saving it, encrypted.
- 3The Loops team the key belongs to appears on the card. Another team = another key = another connection.
What the agent does in Loops
- Reads: every sent campaign with sends, opens, clicks, unsubscribes, bounces and spam reports (and the rates), transactional emails and their delivery numbers, mailing lists, contact properties, audience segments, workflows, the event names Loops has received, and one contact or its suppression status at a time.
- Ordinary changes (your approval setting decides): updating a contact's properties, unsubscribing it or removing it from a list, and creating a contact property.
- Always a person, on every lane: Sending a transactional email and sending an event (an event can start a workflow that emails the contact) — unless it is a dry run, which checks the send and sends nothing.
- Always a person, on every lane: Creating a contact (a new contact is subscribed and can start a "contact added" workflow), subscribing one or adding one to a mailing list.
- Always a person, on every lane: Deleting a contact (it cannot be undone).
What to know
- Numbers are all-time: Loops reports campaign and transactional metrics as totals, not by date — the agent never presents them as "last 7 days".
- People stay masked: a contact's email shows only its first letter and domain; names and custom property values are never returned.
- Never twice: every send carries an idempotency key, so a retried step does not email again. A contact that exists is never created twice.
- Edited in Loops itself: campaign and email content, workflows and themes. Attachments are not sent through Agent Planners.
- Limits: 10 requests a second per team; campaigns, transactional emails and workflows 60 a minute.
Things to ask
- "Which Loops campaign had the best click rate, and which the most unsubscribes?"
- "Is this customer subscribed in Loops, and on which lists?"
- "Check that the password-reset email is published and has every variable, without sending it."
- "Send the onboarding event for this user" — prepared, then a person approves.
Frequently asked questions
- Does Agent Planners support Loops?
- Yes. Connect with a Loops API key; the agent reports on campaigns and transactional emails, reads lists, segments and workflows, and prepares sends a person approves.
- Can the agent send email through Loops on its own?
- No. Sending a transactional email or an event always waits for a person, whatever the approval setting. A dry run checks the send and sends nothing.
- Does the agent see my contacts' personal data?
- No. Contact reads are masked: the first letter and domain of an email, never names or custom property values.