Connects to your stack
58 providers come built in. Four bridges let your agent reach everything else.
73
connected services
499
operations
4
universal connectors
CRM & sales
- Salesforce
- HubSpot
Comms
- Slack
- Microsoft Teams
- Discord
Email & calendar
- Gmail
- Outlook
- Calendly
Developer tools
- GitHub
- GitLab
- Railway
- Vercel
- Sentry
- Linear
- Jira
- Asana
Payments & accounting
- Stripe
- QuickBooks
- Xero
Docs & data
- Notion
- Airtable
- Google Sheets
- Google Drive
- Dropbox
Forms & signing
- Typeform
- DocuSign
Design
- Figma
- Miro
- Canva
The registry spans CRM, project management and comms plus email and storage. Also dev tools, payments and accounting plus e-commerce, design and forms and signing.
Four universal connectors go beyond the built-in integrations. An agent can reach services we’ve never heard of.
Any REST API
Custom REST connections, raw HTTP and an OpenAPI probe that reads a service's spec. The probe auto-maps its operations, so “works with X” holds beyond the 73.
MCP servers
Add remote Model Context Protocol servers via a real handshake. Every agent exposes its own card, so others can use it as a tool.
Agent-to-agent (A2A)
Your agents delegate to one another within your workspace, with an audit trail. Collaboration never leaves your tenant.
SDK bridge
Entity discovery for GitHub and Railway references your real repos and projects. Generic invocation covers the rest.
And events coming the other way
The four above are your agent reaching out. Webhooks let a service reach in and start work here.
- Register a webhook against your agent and pick the events it fires on
- Each one gets a signing secret. You can verify a delivery came from us.
- Choose the signature header and algorithm to match what the sending service expects
- Events can start work. A new row or a finished task triggers the next step.
It won’t fake a broken tool — and it heals itself
The agent always knows whether a connection works. Blips pass, dead tokens fail, fixes heal on the next call.
Connected
Proven recently. The agent uses it without hesitating.
Connectable
The evidence went stale, not bad. The agent still tries — and a successful call re-proves it.
Disconnected
The provider refused outright, so the agent stops trying and tells you plainly. It never pretends.
Press something. Try failing a call twice before you fail it a third time.
Don’t see yours?
Your agent reaches anything with an API
Custom REST, OpenAPI probe, MCP servers and SDK bridge extend the list. Tell us what you need to connect.