Docs · LLMs and developers
Reviewed2026-06-24Version3.12.1Integrations
Native connectors plus a broader catalog and MCP bring live data from your existing tools into Achiral AI.
Connectors bridge your existing tools and Chiro's organizational memory.
The native connectors are registered at application startup and follow the same lifecycle: Connect → Active / Error / Pending / Disconnected. Connect from your organization dashboard under Integrations → Connectors.
How connectors work
Each connector uses OAuth 2.0 to authorize Achiral to receive data on behalf of your organization. After authorization:
- Achiral registers a webhook with the service (where supported) so events arrive in real time.
- For services without inbound webhooks, Achiral polls on a scheduled interval via Agenda.
- Raw events are normalized into a
BusinessEventshape and ingested into your organization's isolated Weaviate tenant. - Chiro draws on this stream when answering questions about your team's activity.
Connectors are scoped to one organization per account. Data from one organization is never shared with another.
Native connectors
| Connector | Method | What Chiro sees |
|---|---|---|
| Slack | Webhook | Messages, channel events |
| Google Workspace | Polling | Gmail, Drive, Calendar |
| GitHub | Webhook | Push, PRs, issues, releases |
| HubSpot | Webhook | Contacts, deals, companies |
| Zendesk | Webhook | Tickets |
| Intercom | Webhook | Conversations, contacts |
| Notion | Polling | Pages, databases |
| Asana | Webhook | Tasks, stories |
| Linear | Webhook | Issues, comments, projects |
| Microsoft 365 | Webhook | Mail, OneDrive, Calendar |
| Jira | Webhook | Issues, comments, projects |
| Salesforce | Polling | Cases, opportunities, leads |
Beyond the native connectors
The native connectors are the deeply integrated set, not a limit. The in-product catalog under Integrations → Connectors lists many more sources across communication, knowledge, engineering, support, CRM, business operations, and database categories. Native connectors use a dedicated connect (OAuth) flow; the other catalog sources are set up as ingestion sources — API sources, webhook presets, and database taps — from the same tab. For anything outside the catalog, connect an MCP server to bring its tools and data into the same organizational memory.
Connection status
Each connector displays one of four statuses in the Integrations tab:
- Active — authorized and receiving data.
- Pending — authorization in progress or webhook registration queued.
- Error — connection lost or token expired. Re-authorize from the Integrations tab.
- Disconnected — manually disconnected; no data is being ingested.
Periodic health checks run automatically. If a connector enters an error state, Chiro continues to work from the data already in your tenant.
Related pages
- Organizations — the admin surface where you connect integrations.
- Security & compliance — data residency, encryption, and audit logs.