Integrations overview

Every tool you can connect to B2B Signals, what each one does, and which way the data moves.

Use this page to pick the right integration and see which way each one moves data. Most are set up in Settings › Integrations. Tools that send people in are also under Sources › Integrations.

What you can connect

Tool	What it does	Data moves	Where you set it up
HeyReach	Sends people to a HeyReach campaign, which then contacts them	B2B Signals → HeyReach	Settings › Integrations
Move from HeyReach	Moves a running HeyReach campaign here, people keep their place	HeyReach → B2B Signals	Campaigns › new campaign
Aimfox	Sends people to an Aimfox campaign, in any of your client workspaces	B2B Signals → Aimfox	Settings › Integrations › More tools
Salesflow	Sends people to a Salesflow campaign	B2B Signals → Salesflow	Settings › Integrations › More tools
Clay	Adds people from a Clay table, with the reason you picked them	Clay → B2B Signals	Sources › Integrations
Zapier, Make, n8n or your own code	Adds people from any tool that can send a web request	Your tool → B2B Signals	Sources › Integrations › API
Calendly or Cal.com	Marks a person as Meeting when they book a call, and stops their follow-ups	Your calendar → B2B Signals	Settings › Integrations
Slack and Telegram	Sends your daily digest and right-away pings to a chat	B2B Signals → Slack or Telegram	Settings › Notifications
Webhooks	Tells your own tools when something happens	B2B Signals → your tool	Settings › Webhooks
MCP	Lets an AI assistant work in your workspace	Both ways	Settings › API & MCP

Who can set them up

Integration	Who can connect or change it
HeyReach, Aimfox, Salesflow, calendar	The workspace owner or an admin. Others see “Only the workspace owner or an admin can change this. Ask them to do it.”
Clay	Anyone can follow the steps. Only an owner or admin can press Turn on, or copy or make the key.
Slack and Telegram	Each member, for themselves. Your channels reach only you.

What you need first

• Clay, and Zapier, Make, n8n or your own code need an API key. “API keys come with a paid plan (Software or Custom).” See API keys.
• HeyReach, Aimfox and Salesflow need your key from that tool, and at least one campaign there that takes new people.
• Calendly needs a paid Calendly plan. Cal.com needs your booking link.

Nothing goes to HeyReach, Aimfox or Salesflow while your workspace is on the Free plan. See Plans.

Website visitors aren’t available yet, even though Settings shows an RB2B tile. See Website visitors.

When a tool stops working

If HeyReach, Aimfox or Salesflow keeps refusing people or not answering, its drawer in Settings › Integrations shows Not working. with the number of people and what to check. One person going through clears it. See HeyReach, Aimfox or Salesflow.

Which sending tool runs the outreach

When you send people to HeyReach, Aimfox or Salesflow, that tool contacts them, not B2B Signals. A person who is also in a campaign here stops in that campaign once they are sent, so nobody gets messages from both. See HeyReach.

Do not contact always applies. A person on it, or at a company on it, is never sent to another tool.

HeyReach

Send new people to a HeyReach campaign.

Move from HeyReach

Bring a running campaign over, paused and in place.

Clay

Add people from a Clay table.

Aimfox

Send people to Aimfox, with the fields you choose.

Salesflow

Send people to a Salesflow campaign.

Add people by API

Zapier, Make, n8n or your own code.

Calendly or Cal.com

Mark booked meetings on their own.

Slack and Telegram

Get your digest in a chat.

API quickstart

Add people and read results with curl.