Integrations
Connected to the systems the work actually lands in
Agents that cannot see your CRM are writing from imagination, and work that cannot reach the channel it was made for is a document nobody opens.
Connect today
HubSpot
One account per client · Live
Read and write the CRM: search contacts, companies and deals, log notes, move deal stages, sync enrichment back. Once approvals are on for your workspace, changes made through the MCP server wait for a person to approve them.
Attio
One account per client · Live
Read and write the CRM: query any object's records, upsert on a matching attribute, attach notes. Once approvals are on for your workspace, changes made through the MCP server wait for a person to approve them.
Slack
One account per client · Live
Deliver agent work where it gets reviewed: post into a channel, read the thread, act on the reply. Once approvals are on for your workspace, posts made through the MCP server wait for a person to approve them.
Apollo.io
One account per client · Live
Prospect data: contact and company search, email enrichment, sequence enrolment.
Searchable
One account per client · Live
Connect your Searchable account to bring its AI-visibility findings into your recommendations. Orbitable only reads: it never changes your Searchable account or shares a report. Each project is bound to one world.
LinkedIn connects separately for social publishing and social selling. Google Ads and Meta are next, and are not available today.
And two ways to reach everything else
MCP server
Every specialist appears as a callable tool inside Claude, Cursor or ChatGPT, loading the right world automatically. Prompts are never logged.
Set it upWebhooks and Make.com
Trigger an agent from a scenario, or fire a signed webhook on every step completion into your warehouse, CRM or Slack. Payloads are HMAC-signed with a per-tenant secret.
How connections are handled
One account per client, not one per provider
Every connection belongs to a world. An agency can hold six separate HubSpot accounts without any of them being able to see another, because the credential is scoped to the world it was added to.
Credentials are encrypted at rest
Stored encrypted per tenant and never returned to the browser after they are saved. A connection can be tested, rotated or removed without anyone reading the secret back.
Agents say when they are guessing
A connected CRM does not mean an agent has queried it. The instructions make the difference explicit, because the alternative is an agent confidently reciting deal numbers it invented.
More on data handling, retention and subprocessors is on the security page.
Start without connecting anything
The world build reads your public site, so the first useful work happens before any credential is involved. Connect the stack once you have decided it is worth it.