TL;DR: Open an audience, scroll to Destinations, click a connector tile, paste the credential, click Connect. The connection belongs to the workspace; the routing and send rules belong to this audience.
Where destinations live
There is no Destinations page and no Destinations entry in Settings. Destinations are configured on an audience — the section is headed Where each member is pushed, with a counter reading N on this audience · N connected in this workspace.
That split is the thing to understand: connecting HeyReach is a workspace-level act you do once, and pointing this audience at a particular HeyReach campaign is per-audience. A second audience reuses the connection and picks its own campaign.
What you can connect today
Seven connectors are live:
Webhook · HeyReach · Prosp · Smartlead · Instantly · Lemlist · Twain
A number of others appear in the grid as planned — HubSpot, Salesforce, Attio, Salesloft, Expandi, Slack, Google Ads, Meta Ads, LinkedIn Ads and Sales Navigator. They're drawn with real logos so you can see what's coming, but they can't be connected yet and clicking them won't open a credential form.
Reading the tiles
Tile appearance | Meaning
Normal | Connectable
Normal, marked as a new integration | Connectable, but nobody has watched a push through end to end yet
Dimmed with a ring | Unavailable — either the provider can't accept an add right now, or we've turned the adapter off
Heavily greyed | Planned. Not connectable
A new integration gets no extra dimming on purpose: it's one click from working.
Connecting
Click a connectable tile. The sheet opens on a Connect view — a short form of credential fields for that provider, usually an API key. Paste it and click Connect.
This is a credential form, not an OAuth handshake. You won't be bounced to the provider's site to authorise anything; you fetch a key from their settings and paste it here.
Configuring the push
Once connected, the sheet gives you the per-audience settings:
- Routing — the target inside the destination. Pick the campaign or list that members of this audience should land in.
- Send rules — two parts. A trigger rule (
Send a member when…, e.g. on first entry) and a release cadence with four options: Immediately, batched in a rolling window (set in minutes, default 60), once a day at a fixed time, or once a week at a fixed time. - Test and push — send a test before you commit.
Save with Save draft while you're still setting up, or Set live when it should start pushing.
Connection health
Each connection reports a health state: Healthy, Degraded, Action required, or Not checked yet. Re-check connection runs the check again on demand.
Pausing, removing, disconnecting
Three different things, and the difference matters:
- Pause connection — the pause control in the sheet header. Stops pushes without losing configuration. The same button resumes it.
- Remove — detaches this destination from this audience. Other audiences using the same connection are untouched.
- Disconnect — drops the workspace connection itself. Every audience using it stops.
What isn't here
Two things people look for in this sheet that the product doesn't have yet:
- No field mapping. You don't choose which Unstuck field lands in which destination field; the connector handles that.
- No overwrite policy. There's no overwrite / append / skip-if-exists control.