Communication
TimelinesAI for AI agents.
Managed auth, ready-made tools.
Read WhatsApp chats, send messages and organize conversations in TimelinesAI on behalf of each of your users.
About TimelinesAI
With the TimelinesAI connector, your agent works with the WhatsApp chats in each user’s own TimelinesAI workspace. It can list chats, read their messages, send a message to a chat or a phone number, and label chats, using only the tools your project allows.
TimelinesAI is a shared inbox that connects WhatsApp numbers to a team and its CRM.
Tools
What your agent can do in TimelinesAI.
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 TimelinesAI connection.
-
List WhatsApp accounts
Readtimelinesai_list_whatsapp_accountsList the WhatsApp numbers connected to the workspace.
-
List chats
Readtimelinesai_list_chatsList WhatsApp chats, with filters such as unread or label.
-
Read a chat
Readtimelinesai_get_messagesGet the messages of one chat.
-
Send a message
Writetimelinesai_send_messageSend a WhatsApp message to an existing chat.
-
Message a phone number
Writetimelinesai_send_message_to_phoneSend a WhatsApp message to a phone number from a connected account.
-
Label a chat
Writetimelinesai_add_chat_labelAdd a label to a chat.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in TimelinesAI, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read chats and messages, and switch off
timelinesai_send_message_to_phoneso it can never start a new conversation. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading chats but not sending messages. A call outside them is refused.
Get started
Connect TimelinesAI
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 TimelinesAI
Each end user authorizes their own TimelinesAI 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 TimelinesAI account, once. const connection = await agent200 .user("user_123") .connect("timelinesai"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the TimelinesAI tools
Name the user, the model and the tools. The model decides which TimelinesAI 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: "Show my unread WhatsApp chats", tools: ["timelinesai"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own TimelinesAI account. Each connection is their own.
-
What access is requested
The connection acts with that user's access in TimelinesAI, such as reading chats, sending messages or managing labels. Users can revoke it later from their TimelinesAI 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 TimelinesAI connector and how to use it.
Connector: TimelinesAI, through Agent200. In code: "timelinesai". What it does: Read WhatsApp chats, send messages and organize conversations in TimelinesAI on behalf of each of your users. Page: https://www.agent200.com/connectors/timelinesai/ 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 TimelinesAI's own page, through the authorization link Agent200 returns. Never ask a user for a TimelinesAI 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: timelinesai_list_whatsapp_accounts, timelinesai_list_chats, timelinesai_get_messages. Write tools: timelinesai_send_message, timelinesai_send_message_to_phone, timelinesai_add_chat_label. Name "timelinesai" 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/timelinesai/framework/claude/ https://www.agent200.com/connectors/timelinesai/framework/chatgpt/ https://www.agent200.com/connectors/timelinesai/framework/claude-code/ https://www.agent200.com/connectors/timelinesai/framework/muse/ https://www.agent200.com/connectors/timelinesai/framework/grok-bot/ https://www.agent200.com/connectors/timelinesai/framework/openai-dots/ https://www.agent200.com/connectors/timelinesai/framework/claude-duet/ https://www.agent200.com/connectors/timelinesai/framework/hermes-agent/ https://www.agent200.com/connectors/timelinesai/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/timelinesai.md
Guides
Use TimelinesAI with the AI you build on.
Step-by-step setup for TimelinesAI with a specific model, assistant or agent framework.
-
TimelinesAI + Claude
How to connect TimelinesAI to Claude
-
TimelinesAI + ChatGPT
How to connect TimelinesAI to ChatGPT
-
TimelinesAI + Claude Code
How to connect TimelinesAI to Claude Code
-
TimelinesAI + Muse
How to connect TimelinesAI to Muse
-
TimelinesAI + Grok Bot
How to connect TimelinesAI to Grok Bot
-
TimelinesAI + OpenAI Dots
How to connect TimelinesAI to OpenAI Dots
-
TimelinesAI + Claude Duet
How to connect TimelinesAI to Claude Duet
-
TimelinesAI + Hermes Agent
How to connect TimelinesAI to Hermes Agent
-
TimelinesAI + OpenClaw
How to connect TimelinesAI to OpenClaw
FAQ
TimelinesAI and Agent200, answered.
Who handles the TimelinesAI 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 TimelinesAI.
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 TimelinesAI connection, never another user's. It cannot reach anything the user or TimelinesAI has not authorized.
Can I limit what my agent can do in TimelinesAI?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.