AchiralAchiral

Docs · LLMs and developers

Version3.12.1

Integrations

Connect external tools so Achiral can use more of your organization's context.

Connectors bring data from your existing tools into Achiral.

Connect them from your organization dashboard under Integrations.

How connectors work

Most connectors follow the same basic flow:

  1. You authorize access.
  2. Achiral starts receiving or syncing data from that tool.
  3. Chiro can use that context when answering questions or building memory.

Connectors are scoped to one organization per account. Data from one organization is never shared with another.

Native connectors

ConnectorMethodWhat Chiro sees
SlackWebhookMessages, channel events
Google WorkspacePollingGmail, Drive, Calendar
GitHubWebhookPush, PRs, issues, releases
HubSpotWebhookContacts, deals, companies
ZendeskWebhookTickets
IntercomWebhookConversations, contacts
NotionPollingPages, databases
AsanaWebhookTasks, stories
LinearWebhookIssues, comments, projects
Microsoft 365WebhookMail, OneDrive, Calendar
JiraWebhookIssues, comments, projects
SalesforcePollingCases, opportunities, leads

Beyond the native connectors

The native connectors are not the only option. The in-product catalog can include more sources across communication, knowledge, engineering, support, CRM, business operations, and databases. For tools outside the catalog, Achiral can also work with API, webhook, database, or MCP-based sources where supported.

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.

If a connector enters an error state, Chiro still works with the data that was already available.

Terminal integrations

For terminal-first workflows, you can connect Warp's Custom Router to the Achiral memory inference endpoint so terminal prompts can use your organization's context.

See Warp terminal for the full setup guide and troubleshooting.

  • Organization — the admin surface where you connect integrations.
  • Warp terminal — use Warp's Custom Router with Achiral memory.