Documentation / Integrations

Integrations: Categories

You connect accounts, the system resolves actions by category — never a hardwired vendor.

You connect accounts, and the system resolves actions by category — never by a hardwired vendor. That’s the platform’s adapter-agnostic ground rule: a column or a playbook asks for “email outreach” or “CRM”, never for a specific name.

Categories

  • Email outreach — your email sending account for cold outreach sequences.
  • LinkedIn — your LinkedIn account for connection requests and message sequences.
  • CRM — your existing CRM, for reading and writing contacts and deal status.
  • Enrichment — contact and company data providers, usable in Columns as enrichment columns or a waterfall chain.
  • Validation — email and phone validation before sending.
  • Research — deep web and company research for qualification and personalization.
  • Calendar — meeting booking and syncing for the meeting flow.
  • Messaging — WhatsApp and other messaging channels.

Why this matters

Switch the provider behind a category — a new email sending account, a different enrichment provider — and nothing changes about your playbooks, columns, and prompts. The category stays the address; only the mapping behind it changes. That’s the difference to building your own toolchain, where you’re the integrator yourself: you connect an account, the system takes care of the wiring.

Connecting

You connect an account in the Integrations area of the web app or through Command (“Connect my LinkedIn account”). Once connected, the category is immediately available to every Playbook and Column that references it — no deploy, no waiting.

See also: Custom Integrations for providers that aren’t already available as a category.