All docs
Connect

Loops: connect with an API key, then report and prepare sends

TL;DR

Loops connects with one API key; the key's team becomes one connection with 14 reads and 6 writes. Sending email and anything that can start a workflow always wait for a person.

Connect step by step

  1. 1In Loops open Settings → API and generate an API key.
  2. 2In Agent Planners open Integrations → Loops, paste the key and press Check and save. The key is checked with Loops first, then stored encrypted and never shown again.
  3. 3Your Loops team appears on the card. Use Refresh accounts after renaming the team in Loops.
  4. 4To replace a key, paste the new one; to stop, press Disconnect (the key keeps working in Loops until you delete it there).

What waits for a person

  • 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.
  • Creating a contact (a new contact is subscribed and can start a "contact added" workflow), subscribing one or adding one to a mailing list.
  • Deleting a contact (it cannot be undone).
Updating a contact's properties, unsubscribing it, removing it from a list and creating a property follow your approval setting. Loops API keys, team settings and attachments are refused.

What the numbers mean

  • Campaign metrics are all-time totals per sent campaign; opens and clicks count a send once. A draft campaign has none.
  • Transactional metrics are totalled across every published version of the email.
  • Only a published transactional email can be sent; the agent checks every data variable it needs before a send.
Tested live on a real Loops team (2026-11-17): every read, and a test contact created, changed, looked up (masked) and deleted. Sends were dry runs only — nothing was emailed. Loops setup guide · Loops platform page · Loops MCP server

About this platform

Related