> ## Documentation Index > Fetch the complete documentation index at: https://docs.b2bsignals.ai/llms.txt > Use this file to discover all available pages before exploring further. # 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](https://docs.b2bsignals.ai/integrations/heyreach.md) | Sends people to a HeyReach campaign, which then contacts them | B2B Signals → HeyReach | **Settings** › **Integrations** | | [Move from HeyReach](https://docs.b2bsignals.ai/integrations/move-from-heyreach.md) | Moves a running HeyReach campaign here, people keep their place | HeyReach → B2B Signals | **Campaigns** › new campaign | | [Aimfox](https://docs.b2bsignals.ai/integrations/aimfox.md) | Sends people to an Aimfox campaign, in any of your client workspaces | B2B Signals → Aimfox | **Settings** › **Integrations** › **More tools** | | [Salesflow](https://docs.b2bsignals.ai/integrations/salesflow.md) | Sends people to a Salesflow campaign | B2B Signals → Salesflow | **Settings** › **Integrations** › **More tools** | | [Clay](https://docs.b2bsignals.ai/integrations/clay.md) | Adds people from a Clay table, with the reason you picked them | Clay → B2B Signals | **Sources** › **Integrations** | | [Zapier, Make, n8n or your own code](https://docs.b2bsignals.ai/integrations/api-intake.md) | Adds people from any tool that can send a web request | Your tool → B2B Signals | **Sources** › **Integrations** › **API** | | [Calendly or Cal.com](https://docs.b2bsignals.ai/integrations/calendar.md) | Marks a person as Meeting when they book a call, and stops their follow-ups | Your calendar → B2B Signals | **Settings** › **Integrations** | | [Slack and Telegram](https://docs.b2bsignals.ai/integrations/slack-and-telegram.md) | Sends your daily digest and right-away pings to a chat | B2B Signals → Slack or Telegram | **Settings** › **Notifications** | | [Webhooks](https://docs.b2bsignals.ai/developers/webhooks.md) | Tells your own tools when something happens | B2B Signals → your tool | **Settings** › **Webhooks** | | [MCP](https://docs.b2bsignals.ai/developers/mcp.md) | 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](https://docs.b2bsignals.ai/developers/api-keys.md). * **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. > [!NOTE] > > Nothing goes to HeyReach, Aimfox or Salesflow while your workspace is on the Free plan. See [Plans](https://docs.b2bsignals.ai/getting-started/plans.md). Website visitors aren't available yet, even though Settings shows an **RB2B** tile. See [Website visitors](https://docs.b2bsignals.ai/sources/integrations.md#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](https://docs.b2bsignals.ai/integrations/heyreach.md#not-working), [Aimfox](https://docs.b2bsignals.ai/integrations/aimfox.md#not-working) or [Salesflow](https://docs.b2bsignals.ai/integrations/salesflow.md#not-working). ## 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](https://docs.b2bsignals.ai/integrations/heyreach.md#a-campaign-of-its-own). [Do not contact](https://docs.b2bsignals.ai/help/glossary.md#do-not-contact) always applies. A person on it, or at a company on it, is never sent to another tool. > [card] [HeyReach](https://docs.b2bsignals.ai/integrations/heyreach.md) > > Send new people to a HeyReach campaign. > [card] [Move from HeyReach](https://docs.b2bsignals.ai/integrations/move-from-heyreach.md) > > Bring a running campaign over, paused and in place. > [card] [Clay](https://docs.b2bsignals.ai/integrations/clay.md) > > Add people from a Clay table. > [card] [Aimfox](https://docs.b2bsignals.ai/integrations/aimfox.md) > > Send people to Aimfox, with the fields you choose. > [card] [Salesflow](https://docs.b2bsignals.ai/integrations/salesflow.md) > > Send people to a Salesflow campaign. > [card] [Add people by API](https://docs.b2bsignals.ai/integrations/api-intake.md) > > Zapier, Make, n8n or your own code. > [card] [Calendly or Cal.com](https://docs.b2bsignals.ai/integrations/calendar.md) > > Mark booked meetings on their own. > [card] [Slack and Telegram](https://docs.b2bsignals.ai/integrations/slack-and-telegram.md) > > Get your digest in a chat. > [card] [API quickstart](https://docs.b2bsignals.ai/developers/quickstart.md) > > Add people and read results with curl. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.