AchiralAchiral

Docs · LLMs and developers

Version3.14.0

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

Integrations

Connectors bring data from your existing tools into Achiral.

Owners and admins connect them for the whole organization under Settings > Connectors (/settings/integrations). Each member can also connect their own accounts from their account page; see Personal connectors.

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 card in Settings > Connectors and on the account Connectors tab shows one of these statuses:

  • Not connected: nobody has authorized the app here.
  • Pending: authorization started but did not finish.
  • Active: Achiral syncs data from the app.
  • Paused: an owner or admin paused the source. Achiral ingests nothing new until someone resumes it.
  • Reconnect needed: the app's credential no longer works. Connect the app again to resume syncing.
  • Error: three syncs in a row failed. Achiral keeps retrying and waits longer after each failure.
  • Archived: someone disconnected the source. Achiral ingests nothing new from it.

Chiro keeps using data Achiral already ingested from a paused, failing, or disconnected source. Disconnecting a source keeps the memories it produced.

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.

  • Connectors — authorize popular apps and tools.
  • Webhooks — receive signed events from external systems.
  • API sources — read records from APIs that are not available as connectors.
  • Database — ingest durable records through read-only database sources.
  • MCP — snapshot resources from connected MCP servers.
  • Observability — remember operational signals from alerting and telemetry systems.
  • Organization — the admin surface where you connect organization connectors.
  • Warp terminal — use Warp's Custom Router with Achiral memory.