Twenty CRM

Twenty is an optional customer system for HivemindOS. Twenty keeps the structured people, company, and opportunity records. HivemindOS adds task routing, company limits, human approvals, and work receipts around those records.

HivemindOS connects to Twenty through its published web APIs. It does not install, embed, or modify the Twenty server. You can use Twenty Cloud or a self-hosted workspace.

Connect Twenty

1. Open a company and choose Connections.
2. In Customers & deals, choose Connect Twenty.
3. Sign in with Twenty, or paste an API key created in Twenty’s APIs & Webhooks settings.
4. Leave the default cloud address, or enter the address of your self-hosted workspace.
5. Wait for the live connection check, then choose Use for company.

Use a Twenty role that can reach only the records this hive needs. The credential stays in HivemindOS’s shared credential store and is never returned to an agent.

The company card shows bounded people, company, and deal counts plus recent opportunities. The Sales view also treats the assigned Twenty workspace as an available pipeline source.

Live Updates

Twenty can notify HivemindOS when a record changes:

1. Save the webhook secret while connecting Twenty.
2. In the company connection card, choose Copy live-update address.
3. Add that address and the same secret in Twenty’s APIs & Webhooks settings.

The address must be reachable from the internet for Twenty Cloud to call it. HivemindOS rejects unsigned, stale, oversized, and malformed notifications. It stores a bounded receipt rather than copying the full customer record into the notification log.

What Agents Can Do

Reading and changing records are separate capabilities.

• Reads return bounded summaries of people, companies, and opportunities.
• Creates, updates, and deletes require an exact human confirmation and a retry-safe idempotency key.
• Company agents must act from an active Work Board task assigned to a member of that company.
• Each company call is checked against its integration request limits before it reaches Twenty.
• Disconnecting Twenty removes its saved access, refresh, workspace, and webhook credentials. It does not delete records already stored in Twenty.

One connected Twenty workspace can be assigned to more than one company. Do that only when those companies are intentionally meant to share the same customer system.