For the complete documentation index, see llms.txt. This page is also available as Markdown.

Destinations vs live channels

The two ways data moves: live channels that act in real time, and destinations that sync in batches.

For warehouse workspaces.

Data leaves the platform two ways, and the difference is simple. A live channel acts the moment a decision happens. A destination receives batches on a schedule.

Live channels

Live channels are the tools the system acts into in real time:

  • your CRM (HubSpot or Salesforce),

  • ad platforms (LinkedIn, Meta),

  • outbound (Instantly).

When a play decides to act, the action executes synchronously: a contact is routed, an audience is pushed, a sequence starts. The result comes back into the trace immediately.

Destinations

Destinations are batch pipelines: scheduled syncs that move data in bulk.

  • Into the platform from your sources, or out to your warehouse.

  • Each pipeline has a schedule and a job history (rows, duration, status).

  • Any pipeline can be triggered on demand.

Use destinations for data movement. Use live channels for action.

Connection health

Every connection reports a status: active, pending, expired (re-consent needed, select Reconnect), revoked, or error. Statuses surface in Your stack, and failures raise a hand in Pulse rather than failing silently.

Outside the app

Pipelines and channel actions can be managed outside the app via API and MCP as well.

Last updated