Loops.so + Claude Code
Build a Loops.so agent with Claude Code
Set up Loops.so for Claude Code with Agent200, then check which tools are available to your agent.
On this page
Overview
This guide has Claude Code build a Loops.so agent with the Agent200 SDK, in your own project. When you finish, your agent can call the Loops.so tools for each of your users.
Claude Code writes the code from the steps below; Agent200 runs the Loops.so calls with each user's own connection and handles the OAuth flow and the tokens. You do not build or maintain a Loops.so integration.
- Connector
- Loops.so
- Works with
- Claude Code ยท Coding agent, with the SDK
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 7 tools
- Model in examples
openai/gpt-5.6-sol
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Loops.so enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Loops.so account. They approve access once, on Loops.so's own page.
- Claude Code in your project. It writes the code with the Agent200 SDK; you review it.
Connect Loops.so to Claude Code
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Loops.so and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Give this guide to Claude Code
Start Claude Code in your project and paste the agent brief from this page, or give it the address of this guide's Markdown version. Claude Code follows the steps below in order: the SDK, the Loops.so connection and the first request. Review the code it writes before you run it.
-
3
Step 3: Set up the Agent200 SDK
Add the SDK to your project and create a client with the key from the environment.
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, }); -
4
Step 4: Let your user connect Loops.so
Each end user authorizes their own Loops.so account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Loops.so's own page. Agent200 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); } -
5
Step 5: Run with the Loops.so tools
Name the user, the model and Loops.so in the tools. The model decides when a Loops.so tool is needed, and Agent200 executes the call with the user's own 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);
Test your connection
Run one request to check everything is wired up.
Ask
Ask Claude Code to list the Agent200 tools available for Loops.so, including which are read-only.
What should come back
- A list of the Loops.so tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
If no tools appear, check your Agent200 project access for Loops.so and make sure its tools are enabled. Tool availability depends on your project setup.
Get your API key
Create a key in the Agent200 dashboard. It reaches Loops.so and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Loops.so to Claude Code.
Goal: connect Loops.so to Claude Code with Agent200. Guide: https://www.agent200.com/connectors/loops-so/framework/claude-code/ 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. Make sure Loops.so is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs. 3. Add the Agent200 SDK to the project and create a client with that key. 4. Give every request a stable id for the end user. Agent200 uses only that user's own connections. 5. Connect the user's Loops.so account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Loops.so. 6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "loops_so" in the tools. The model decides when a Loops.so tool is needed; Agent200 executes the call. 7. Check it works with this request: "Ask Claude Code to list the Agent200 tools available for Loops.so, including which are read-only." What should come back: - A list of the Loops.so tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled. 8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Loops.so, then retry. The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
The whole guide is also available as Markdown, for agents and LLMs: /connectors/loops-so/framework/claude-code.md
Loops.so tools Claude Code can call
-
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.
How it works
-
01
Your app sends the request
It calls Agent200 with the model, instructions, the input, the end user's id and the Loops.so tools.
-
02
The model picks a tool
The model decides whether a Loops.so tool is needed, and with which arguments.
-
03
Agent200 runs the call
It uses that user's own Loops.so connection, within the endpoints and scopes your project allows, and returns the result to the model.
-
04
Your app gets the result
Agent200 returns the completed result. Your app decides when the agent runs and what happens next.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Loops.so account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Loops.so enforces what its API grants.
Troubleshooting
The request says Loops.so authorization is required
The end user has not connected Loops.so yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Loops.so's own page, then run the request again.
Claude Code does not use the Loops.so tools
Check that Loops.so is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Loops.so in the request, or in the instructions, also helps the model choose the right tool.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows (services, endpoints and scopes), and Loops.so returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Loops.so again so they can approve the new access.
The results come from the wrong account
Every request names an end user (user_123 in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Loops.so connection, never another user's.
The API key was pasted into a chat or committed
Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.
