Integrations
Add integrations on the Integrations page, then choose them as destinations on each agent. Secrets are stored encrypted.
Every push is logged with its response. Failed pushes are retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours.
Sequencers
| Integration | What happens on approval | You need |
|---|---|---|
| OutreachSender | The lead is enrolled, with the AI message as step 1 (or your sequence) | OutreachSender URL and an API key with scope multichannel |
| ReachDak | The lead is added to a LinkedIn campaign | URL, API key, campaign id |
| Instantly | The lead is added to a campaign (needs an email) | API key (v2), campaign id |
| Smartlead | The lead is added to a campaign (needs an email) | API key, campaign id |
| lemlist | The lead is added to a campaign (needs an email) | API key, campaign id |
| HeyReach | The lead is added to a LinkedIn campaign (needs a LinkedIn URL) | API key, campaign id (a number) |
HeyReach is your own LinkedIn tool and runs on your account under its terms. ReadyBuyerFinder itself never logs in to or automates LinkedIn.
CRMs
| Integration | What happens on approval | You need |
|---|---|---|
| HubSpot | The contact is created or updated by email, with a note giving the score and why-now reasons | Private app token with crm.objects.contacts.write |
| Pipedrive | An organisation, a person and a note | API token |
| Salesforce | A Lead (source "ReadyBuyerFinder") with the score and why-now reasons in the description | Instance URL, connected app consumer key and secret, a refresh token; login URL https://test.salesforce.com for a sandbox |
| Attio | The person is matched or created by email, with a note | Access token with record and note read-write scopes |
| Zoho CRM | A Lead (source "ReadyBuyerFinder") with the reasons in the description | Data centre (in, com, eu, com.au, jp or ca), self-client id and secret, refresh token with ZohoCRM.modules.leads.CREATE |
ReadyBuyerFinder only pushes. It never overwrites fields in your CRM.
Alerts
| Integration | What you get | You need |
|---|---|---|
| Slack | An alert for every new lead and every reply | Incoming webhook URL |
| Telegram | An alert for every new lead and every reply | Bot token and chat id |
| An alert for every new lead and every reply, through Meta's WhatsApp Cloud API | Your phone number id, an access token, and the number to alert |
WhatsApp only allows free-form messages inside its 24-hour window. Outside it, you need a pre-approved template with one body variable; enter its name and language code, and ReadyBuyerFinder puts the alert text in that variable.
Everything else
| Integration | What happens | You need |
|---|---|---|
| Webhook | A signed JSON lead.approved POST. Works with Make, n8n, Clay and any tool that accepts webhooks | URL |
| REST hooks | Zapier, Make and n8n subscribe to lead.created, lead.approved or reply.received. See Zapier, Make and n8n | An API key |
| CSV | Export leads from the Leads page | – |
| MCP | Claude, ChatGPT and other assistants read and act on leads. See MCP server | An API key |
Replies coming back
OutreachSender and ReachDak can post events back to ReadyBuyerFinder: replied, bounced, unsubscribed, meeting booked. To set this up, copy the inbound URL and secret from the integration's page into the sequencer. Replies land in the Replies inbox with a label. An unsubscribe, or a reply asking to stop, suppresses the person in every agent.
Microsoft Teams
Alerts for new leads and replies as an Adaptive Card with an Open lead button. Paste either a Teams incoming-webhook URL (…webhook.office.com/…) or a Workflows / Power Automate URL ("Post to a channel when a webhook request is received", …logic.azure.com/…).
Clay table
Sends each approved lead to a Clay table as one flat row (first_name, last_name, title, email, email_status, linkedin_url, company, company_domain, country, score, signal, signal_url, why_now, icebreaker, subject, first_message, lead_url, external_id). In Clay: Add source → Webhook, copy the URL, and paste the auth token if you set one.
When a push fails
Pushes retry after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. If the last retry fails, the lead shows "failed", the delivery log keeps the error, and the workspace's owners and admins get an email (at most one per destination per day).