> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traxy.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Claude, traxy, and HeyReach
This workflow connects traxy to HeyReach so qualified leads flow straight into your campaigns, then connects HeyReach to Claude so you can manage that pipeline conversationally.
In HeyReach, go to **Settings → Integrations**, then select **HeyReach API**.
Click **New API key** to generate one (this invalidates any previous key), then copy it.
Back in traxy, go to **Integrations → HeyReach**.
1. Paste your HeyReach API key into the **API connection** field and click **Connect**.
2. Under **Destination**, set the **Destination type** to `Campaign` and select (or create) the campaign traxy should send leads to.
3. Under **Delivery**, choose **Manual** (send leads yourself from the Leads table) or **Auto** (send every new lead above your ICP match threshold automatically).
4. Click **Save settings**.
Still in HeyReach, go to **Settings → Integrations → HeyReach MCP Server**.
Copy the **MCP Connection URL** (it already includes your MCP key, e.g. `https://mcp.heyreach.io/mcp?xMcpKey=...`).
In Claude, open **Settings → Connectors → Add → Add custom connector**.
1. Name it `heyreach`.
2. Paste the MCP Connection URL into the **Remote MCP server URL** field.
3. Leave OAuth fields blank — the key is already in the URL.
4. Click **Add**.
Claude will show "You are not connected to heyreach yet." Click **Connect**. Since the key is embedded in the URL, the connection completes immediately — no separate authorization screen.
With traxy delivering leads into your HeyReach campaign and HeyReach connected to Claude, open a new chat and run the following prompt:
```text theme={null}
Select the best [X] leads from Traxy for a HeyReach LinkedIn outreach campaign and set up personalized messaging for them.
Lead selection: Pull all PRIORITY-tier leads first. Fill remaining slots up to [X] with the highest ICP-match-% leads from QUALIFIED tier. Exclude anything not disposition ACTIVE, and exclude leads without a usable LinkedIn profile URL.
Personalization: Use name, title, and company as baseline merge fields ({{firstName}}, {{jobTitle}}, {{companyName}}) for every lead. For leads where Traxy's signal data includes a specific, real reference (e.g. a named post, author, or topic they engaged with — not a generic "active ICP engager" summary), also write a one-line custom field (signalLine) referencing that specific engagement, and weave it into the message. For leads with only generic signal data, skip the signal line and rely on the name/title/company personalization — don't fabricate specificity that isn't there. Flag which leads got which treatment.
Build in HeyReach: Add the leads (with their custom fields) to a list or directly to a campaign via add_leads_to_list_v2 / add_leads_to_campaign_v2 (max 100 per call, so this fits in one batch). Draft one message template with the merge tags embedded in natural sentences, not bolted-on greetings. Check the campaign's existing sequence first (get_campaign_sequence) before writing a new one, so the personalized message step fits into whatever connection-request/follow-up structure already exists — build a new one only if none exists. Assign a LinkedIn sender account to the campaign. Preview the merged output on a handful of real leads to catch blank fields or broken sentences before anything goes live. Confirm daily send/invite volume stays within safe LinkedIn limits.
Before launching: Show me the selected lead list and the drafted message(s) for approval — don't start the campaign automatically.
```
## Next steps
With both connections in place, traxy pushes qualified leads into your HeyReach campaign automatically (or on your review), and Claude can query and act on that HeyReach data directly — checking campaign status, adding leads, or reporting on outreach performance.