Help Scout
Read and reply to conversations, add notes, change status and find customers in Help Scout on behalf of each of your users.
Connectors
Give your agent the chat, meeting and support channels your users work in. Each user connects their own account through managed OAuth, and your agent calls ready-made tools through one SDK and one API key.
25 to 28 of 28 connectors
Read and reply to conversations, add notes, change status and find customers in Help Scout on behalf of each of your users.
Find and update contacts, tag them, send messages and close conversations in respond.io on behalf of each of your users.
Find, create and update incidents, add comments and search knowledge articles in ServiceNow on behalf of each of your users.
Start outbound voice calls, read call transcripts and manage voice assistants in Vapi on behalf of each of your users.
Missing a service?
Tell us what your agent needs to reach. The list grows with what developers ask for.
Guides
Step-by-step setup for a connector with a specific model, assistant or agent framework.
How to connect Notion to Claude
How to connect Slack to Muse
How to connect GitHub to Claude Code
How to connect Gmail to ChatGPT
How to connect Google Drive to Hermes Agent
How to connect Linear to OpenClaw
How it works
Every connector on this page works the same way, so adding the next one takes no new integration work.
Enable the services your agent needs in your project, and choose which of their tools it may call.
For services that use managed OAuth, every end user approves access on the service's own page. Agent200 stores the tokens and keeps them fresh.
Through the Agent200 SDK or MCP server, with one API key. Agent200 runs each call with that user's own connection, within the endpoints and scopes you allow.
Agent200 handles each provider's API, its OAuth flow and every end user's connections. You choose what your agent can reach.