Communication
Loops.so for AI agents.
Managed auth, ready-made tools.
Add and update contacts, send events and transactional emails in Loops on behalf of each of your users.
About Loops.so
With the Loops.so connector, your agent manages contacts and email in each user’s own Loops account. It can add, find, update or remove a contact, send an event that starts a loop and send a transactional email, using only the tools your project allows.
Loops.so is an email platform for software companies that send product, marketing and transactional email.
Tools
What your agent can do in Loops.so.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Loops.so connection.
-
Find a contact
Readloops_so_find_contactFind a contact by email address or user ID.
-
Create a contact
Writeloops_so_create_contactAdd a new contact to the audience.
-
Update a contact
Writeloops_so_update_contactChange a contact's properties or list subscriptions.
-
Delete a contact
Writeloops_so_delete_contactRemove a contact from the audience.
-
Send an event
Writeloops_so_send_eventSend an event for a contact to trigger a loop.
-
Send a transactional email
Writeloops_so_send_transactional_emailSend a transactional email from a published template.
-
List mailing lists
Readloops_so_list_mailing_listsList the mailing lists in the account.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Loops.so, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent add and update contacts, and switch off
loops_so_delete_contactso it can never remove one. -
Restrict what the agent reaches
Choose the endpoints a project may use, for example contacts and events but not transactional email. A call outside them is refused.
Get started
Connect Loops.so
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Loops.so
Each end user authorizes their own Loops.so account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Loops.so account, once. const connection = await agent200 .user("user_123") .connect("loops_so"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Loops.so tools
Name the user, the model and the tools. The model decides which Loops.so tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Add jane@acme.com to Loops as a new trial user", tools: ["loops_so"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, connecting their own Loops account. Each connection belongs to that user.
-
What access is requested
Access to the parts of their Loops account the connection needs, such as contacts, events and transactional email. Users can revoke it later from their Loops account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Loops.so connector and how to use it.
Connector: Loops.so, through Agent200. In code: "loops_so". What it does: Add and update contacts, send events and transactional emails in Loops on behalf of each of your users. Page: https://www.agent200.com/connectors/loops-so/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Loops.so's own page, through the authorization link Agent200 returns. Never ask a user for a Loops.so password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: loops_so_find_contact, loops_so_list_mailing_lists. Write tools: loops_so_create_contact, loops_so_update_contact, loops_so_delete_contact, loops_so_send_event, loops_so_send_transactional_email. Name "loops_so" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/loops-so/framework/claude/ https://www.agent200.com/connectors/loops-so/framework/chatgpt/ https://www.agent200.com/connectors/loops-so/framework/claude-code/ https://www.agent200.com/connectors/loops-so/framework/muse/ https://www.agent200.com/connectors/loops-so/framework/grok-bot/ https://www.agent200.com/connectors/loops-so/framework/openai-dots/ https://www.agent200.com/connectors/loops-so/framework/claude-duet/ https://www.agent200.com/connectors/loops-so/framework/hermes-agent/ https://www.agent200.com/connectors/loops-so/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/loops-so.md
Guides
Use Loops.so with the AI you build on.
Step-by-step setup for Loops.so with a specific model, assistant or agent framework.
-
Loops.so + Claude
How to connect Loops.so to Claude
-
Loops.so + ChatGPT
How to connect Loops.so to ChatGPT
-
Loops.so + Claude Code
How to connect Loops.so to Claude Code
-
Loops.so + Muse
How to connect Loops.so to Muse
-
Loops.so + Grok Bot
How to connect Loops.so to Grok Bot
-
Loops.so + OpenAI Dots
How to connect Loops.so to OpenAI Dots
-
Loops.so + Claude Duet
How to connect Loops.so to Claude Duet
-
Loops.so + Hermes Agent
How to connect Loops.so to Hermes Agent
-
Loops.so + OpenClaw
How to connect Loops.so to OpenClaw
FAQ
Loops.so and Agent200, answered.
Who handles the Loops.so OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Loops.so.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Loops.so connection, never another user's. It cannot reach anything the user or Loops.so has not authorized.
Can I limit what my agent can do in Loops.so?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.