Plug into the apps you already run
27 knowledge-base connector families plus 9 messaging and delivery apps—each with full-color marks below. Connections are created per agent from Automations, using the same OAuth, API key, and webhook patterns you will see after sign-in.
Apps with connector flows (36)
Logos are fetched via our proxied brand endpoint for accurate color; third-party marks belong to their owners.
- Open Connections from any agent's Automations area—the catalog is grouped the same way as in the live product
- OAuth, API keys, and (for some apps) webhooks match what the connection manager actually offers today
- Knowledge-oriented apps can feed sync jobs into your bases; messaging apps power where conversations happen
- Disconnect, rotate keys, or add a second workspace without touching unrelated agents
Signed in? Open an agent, then Automations → Connections to browse the live catalog.
In the dashboard
Connect once per agent, with the right auth for each app
The same automation catalog you see after signing in drives this page. Pick an app, complete OAuth or paste keys, and we keep the link scoped to that agent unless you connect again elsewhere.
Start from the agent
Each agent has an Automations workspace with a Connections entry point—exactly where your team wires Slack, Notion, Zendesk, or Twilio without hunting through unrelated settings.
- Browse by category: messaging, knowledge base, CRM, e-commerce, storage, calendar
- See what is already linked and which apps still need credentials
- Jump back to knowledge bases or deployments from the same sidebar
OAuth where the platform supports it
For vendors that expose standard OAuth, we send people through the official consent screen and store refresh-friendly tokens for that connection.
- Slack, Discord, Microsoft Teams, Meta (Messenger / Instagram), Google, Dropbox, Box, and many CRM or commerce surfaces
- Redirect URLs return you to the same agent automations view you left from
- Reconnect flows reuse the same pattern when tokens expire or scopes change
API keys & structured fields
When an app expects a bot token, subdomain, or account SID, the connection dialog asks for those fields explicitly—no fake "OAuth" button.
- Telegram, WhatsApp Business, Twilio SMS, SendGrid, Zendesk, ServiceNow, and similar patterns
- Extra inputs (subdomain, store URL, instance host) are validated before we mark the connection active
- Keys can be rotated from the same modal without deleting the whole automation graph
Knowledge sync + automations, one catalog
Many apps both ingest content into knowledge bases and participate in trigger/action automations. You connect credentials once per agent; the product decides which jobs are allowed.
- Scheduled or on-demand sync pulls docs, tickets, files, or catalog data into chunks you can search
- Separate automation definitions can call the same connection for outbound messages or CRM updates
- Webhook-style apps can participate as triggers when you build the automation—no connection object required
After connecting
Grounded answers, proactive automations, and real channels
Connectors are not vanity badges—they change what assistants can read, what workflows can fire, and where end users actually chat with your agent.
Knowledge that stays honest
Documentation, support, commerce, CRM, file, and calendar connectors keep retrieval aligned with the systems your company already maintains.
- Multiple bases let you separate public help from internal runbooks
- Provenance stays tied to sources so teams know which sync job produced a chunk
- Uploads and crawls mix freely with connector-backed documents in the same base
Automations that touch live systems
Triggers and actions are backed by the live automation catalog—apps, events, and payloads vary by integration, but everything flows through the same connection objects.
- Use connected identities when an action needs to post or update something on your behalf
- Keep experimental workflows on staging agents with different connections than production
- Add automations without redeploying the website widget or API surface
Omnichannel without duplicate training
Messaging connectors let the same brain answer on the web, in Slack, on WhatsApp, or over SMS—each channel respects the agent configuration you already set.
- Web widget, hosted pages, and API deployments reuse the same knowledge and tools
- Channel-specific rate limits and compliance still apply at the vendor
- Turn channels on or off per agent as you roll out
Knowledge-oriented
Connector families that feed your bases
Docs portals, tickets, commerce catalogs, CRM objects, files, and calendars—each row uses the same full-color logo pipeline as the dashboard.
Documentation & support
Notion
Zendesk
Confluence
ServiceNow
Slite
ClickUp
Intercom
Help Scout
Freshdesk
Commerce & catalogs
Shopify
WooCommerce
BigCommerce
Magento
CRM & marketing
Salesforce
HubSpot
Pipedrive
Zoho CRM
Files & collaboration
Google Drive
Dropbox
Box
OneDrive
Calendars & booking
Apple / iCloud Calendar
Calendly
Cal.com
Conversations
Messaging & channels
Wire the same assistant into Slack, Discord, Teams, WhatsApp, SMS, email, and social messaging—connections are managed next to your other automations.
Slack
Discord
Telegram
WhatsApp Business
Facebook Messenger
Instagram
Twilio SMS
SendGrid
Pair connectors with grounded retrieval on Knowledge & RAG, compare limits on pricing, or walk the full surface on features.
Next step
Connect apps, then attach knowledge to an agent
Create a workspace, open an agent, add Connections for the systems you trust, and point a knowledge base at the same sources your customers ask about.