Agent Serve · Integrations
Agent Serve agents read and act across your CRM, messaging, warehouse and documents. Connect a tool once; every agent can use it.
Agent Serve integrations connect business applications to Agent Serve, the AI workspace where teams build, deploy, and manage AI agents, as blocks with actions and real-time triggers that agents and workflows use.
262
integrations
5,000+
actions agents can take
62
with real-time triggers
56
connect with one-click OAuth
How it works
Agent Serve turns a connected tool into actions an agent can call and events that can start a run.
Sign in with OAuth or add an API key. Agent Serve stores the credential encrypted.
Add members to the credential, so the right people in the team space can use it in their agents.
Give an Agent block the tools it needs and a goal in plain language. It decides which actions to call, and in what order.
A real-time trigger starts the run from an event, and outbound messages can wait for a person to approve them.
Categories
Agent Serve integrations cover 16 categories, from sales and support to data, security, and developer tools.
Catalog
Search by tool, action, or trigger — each page lists exactly what Agent Serve agents can do with it.
14 of 262 integrations
Manage email inboxes, threads, and messages with AgentMail
Send emails and manage templates with AWS Simple Email Service
Manage Email Bison leads, campaigns, replies, and tags
Send, read, search, and move Gmail messages or trigger workflows from Gmail events
Manage Instantly leads, campaigns, emails, and lead lists
Manage outreach activities, leads, and send emails via Lemlist
Manage contacts and send emails with Loops
Manage audiences, campaigns, and marketing automation in Mailchimp
Send emails and manage mailing lists with Mailgun
Send, read, search, reply, organize, and manage Outlook email and calendar
Send emails and manage contacts with Resend.
Send emails and manage contacts, lists, and templates with SendGrid
Manage Smartlead cold email campaigns, sequences, and leads
Send emails via any SMTP mail server
Combinations
Agent Serve workflows chain integrations together, so one event in a tool can drive the next step in another.
Agent Live
Agent Live, our real-time assistant for sales and support calls, reuses the connections your team sets up in Agent Serve.
About Agent Live
In depth
How Agent Serve starts runs from your tools, lets agents act in them, and keeps a person in the loop.
Agent Serve integration triggers start a workflow when something happens in the tool, such as a new message, ticket or deal update.
An Agent Serve Agent block receives the integration tools you allow and decides which to call, in order, from the goal you describe.
When an Agent Serve Relay sends email from Gmail or Outlook, a reviewer approves the exact message first, under every autonomy setting.
Beyond the catalog
When a tool is not in the catalog, Agent Serve still reaches it through its API, webhooks, your own code or a shared tool standard.
The Agent Serve API block calls any REST endpoint with GET, POST, PUT, DELETE or PATCH, query parameters and headers.
POST https://core.example.com/v2/cases
The Agent Serve Webhook block sends signed payloads, and Webhook Trigger receives events from any service, with an optional authentication token.
Webhook URL · Payload · Signing Secret
Write your own tool for Agent Serve agents in Settings → Custom tools: a title, a JSON schema and the code it runs.
lookup_policy_holder(policy_id)
MCP is a standard way for AI apps to share tools. Agent Serve connects to MCP servers in Settings → Tool connections, so agents can use their tools.
Streamable HTTP · headers or OAuth
Agent Serve can expose a team space’s workflows as tools on its own MCP server, for other AI apps to call.
Settings → MCP servers
Each Agent Serve credential has members with an admin or member role. Team space admins manage every credential.
Settings → Secrets · Members (3)
Under the hood
| Authentication | OAuth sign-in, API key, or no authentication, depending on the tool. |
|---|---|
| Credentials | Encrypted at rest, shared at team space level with named members, or kept personal. |
| Triggers | Real-time triggers on many integrations, plus Webhook Trigger for events from any service. |
| Duplicate events | Webhook Trigger skips repeats of a chosen deduplication field for 7 days. |
| Any REST API | The API block, with GET, POST, PUT, DELETE and PATCH, query parameters and headers. |
| MCP servers | Connect over Streamable HTTP with no auth, headers or OAuth; expose workflows as tools. |
| Custom tools | A title, JSON schema and code, defined per team space. |
| Catalog | One page per integration, listing its actions, triggers and authentication. |
Governance
Agent Serve access policies narrow integrations and tools per group, and credentials stay with the people they are shared with.
Security and governanceAgent Serve access policies list the integrations a group may use, deny single tools, and can switch off MCP tools, custom tools and webhook triggers.
An Agent Serve access policy can hide personal credentials, so a group works only with credentials shared in the team space.
Whoever runs an Agent Serve deployment can limit MCP server connections to an allowlist of domains.
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
Run Agent Serve in your own cloud or data centre, next to the systems it reads.
Before and after
| Work | Before | With Agent Serve |
|---|---|---|
| Connecting a tool | BeforeA script per tool, each with its own copy of the key. | With Agent ServeOne credential in Agent Serve, shared with named members. |
| Deciding what to call | BeforeHard-coded steps that break when the case changes. | With Agent ServeAn agent picks the actions it needs from the tools you allow. |
| Reacting to events | BeforePolling jobs that run late or twice. | With Agent ServeReal-time triggers, with duplicate events skipped. |
| Messages to clients | BeforeSent by a script with no one checking. | With Agent ServeRelays wait for a person to approve the exact email. |
Works with
Each integration is a block with actions and triggers in the workflow builder.
Chat calls integration tools and connects MCP servers and OAuth apps for you.
Relays send email and book meetings through Gmail, Outlook and Google Calendar, with approval.
The model in each Agent block decides which integration tools to call.
Further reading
Disputes that fail reconciliation tend to sit in a side queue until the chargeback window has closed. Here is an end-to-end setup that finds them early, ranks them by deadline and drafts the pack, with an analyst signing every filing.
Cards and payments operations · 12 min readPeriodic reviews pile up because every file starts from scratch, even when nothing has changed. Here is a setup that refreshes the data, drafts the file and routes it by risk, so analysts spend their time on the reviews that need judgement.
Retail and business banking · 12 min readSampled call reviews find a missing risk warning weeks after the client acted on the advice. Here is a setup that checks every recorded advice call within a day and puts the quote in front of a compliance reviewer.
Wealth and advice · 12 min readQuestions
Each integration is a block you drag onto Agent Serve's workflow builder. Together, Agent Serve's 262 integrations expose 5013+ tools that AI agents can call. 56 connect with one-click OAuth, and the rest use an API key or no authentication at all. Wire blocks together, add an AI agent block for reasoning, and run.
Start with the systems your process already depends on. Request access to review supported actions, authentication requirements, and deployment options with our team. Third-party service charges may apply.
Yes. This is the core of Agent Serve. You give an agent access to integration tools and describe the goal in plain language; the agent decides which tools to call, in what order, and how to handle the results. You choose which tools are available and define the instructions for the task.
Yes. 62 Agent Serve integrations include real-time webhook triggers. Add a trigger block to your agent, copy its webhook URL into the external service, and matching events can start the configured workflow. Trigger support varies by integration.
Agent Serve supports 262 integrations across messaging, CRMs, databases, developer tools, AI providers, and more, and the catalog grows continually. If a tool you need is missing, request it below and we can discuss your requirements.
Missing a tool?
Tell us what your team uses and we’ll prioritise it. Agent Serve can also call any REST API directly while an integration is on the way.
Enterprise access
Agent Serve is available to teams by invitation. Tell us what you want to build and we will set up your workspace with you.