Integrations overview
Every way to connect Blue Reacher to the tools you already run: native GoHighLevel, per-platform setup guides, no-code automation, and the raw API for anything else.
Every integration does the same two things: send a message when something happens in your system, and write the reply back when it arrives. What changes is where the buttons are.
Pick your path
Two kinds of connection exist. Native integrations are connected for you during onboarding and sync conversations into the CRM with nothing to host. API builds are patterns you (or your automation tool) wire against the REST API.
| Your setup | Start here | Kind |
|---|---|---|
| GoHighLevel | GoHighLevel | Native, two-way sync and workflow actions |
| HubSpot | HubSpot | Native inbox sync, plus an API path for workflow sends |
| Salesforce | Salesforce | Native timeline sync with embedded replies, plus a Flow path |
| Close | Close | Native, lead activity feed |
| Pipedrive | Pipedrive | Native, contact timelines |
| Follow Up Boss | Follow Up Boss | Native, logged as real texts |
| Jobber | Jobber | Native, client timelines (beta) |
| Facebook and Instagram lead ads | Meta lead forms | Native, form submission to first message |
| Zapier | Zapier | API build |
| n8n | n8n | API build |
| Make | Make | API build |
| Shopify | Shopify | API build over Shopify webhooks |
| An AI assistant (Claude, Cursor) | MCP server | Native, one endpoint |
| Anything else, or in-house software | Connecting other CRMs | API build |
Beyond the CRM
The platform also connects outward. These are configured on your account rather than built:
- Slack. New-lead alerts, reply notifications, and automation updates routed to the channels your team watches.
- Line-type lookup. Numbers are identified as mobile, landline, or VoIP before they enter a messaging flow, so landlines never eat an iMessage send.
- AI on your own key. AI-assisted replies and analysis can run on your own OpenAI, Anthropic, or Google AI account, so usage and data terms are yours.
Ask your account manager to turn any of these on.
The three things every integration needs
- An API key. Build against a
brk_test_key first; it simulates every send. Server-side only. - An HTTPS endpoint that accepts POST, returns
200fast, and verifies the signature. Registered with us during onboarding or from the dashboard. - Sends default to the drip lane, which paces and load-balances across your lines for you; there is no line ID to manage unless you want to pin one.
The identifier that makes it all work
Stamp your CRM record ID into the contact's custom_fields (one upsert to POST /v1/contacts) and carry it in send metadata. Webhook events identify the contact by contact_id and phone_number; your handler resolves either to the CRM record via your stored mapping. Get this right at the start and every integration below is a wiring exercise. The full pattern is in connecting other CRMs.
What to check before you go live
- One test-key message end to end through the automation, response parsed
- One live message, confirmed on the CRM record
- A real reply from a device, confirmed landing within seconds
- A deliberately broken signature, confirmed rejected with
401 - A deliberate
500from your handler, confirmed retried, and your write confirmed idempotent onmessage_id - The automation enabled for one small segment before the whole list