> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/integrations/destinations-vs-live-channels.md).

# Destinations vs live channels

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

{% hint style="info" %}
**For warehouse workspaces.**
{% endhint %}

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.**

{% columns %}
{% column %}

## 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.
{% endcolumn %}

{% column %}

## 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.
{% endcolumn %}
{% endcolumns %}

## Connection health

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

{% hint style="warning" %}
A workspace connects one CRM, HubSpot or Salesforce, not both. Pick the system of record. The platform writes back to it and never overwrites sales-owned fields.
{% endhint %}

## Outside the app

Pipelines and channel actions can be managed outside the app via [API](/settings/api-keys.md) and [MCP](/iharness/bring-your-own-agent.md) as well.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aloop.icustomer.ai/integrations/destinations-vs-live-channels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.