HeyReach

Generate Your HeyReach API Key

Navigate to your HeyReach account settings and locate the API section. Generate a new API key and store it securely — this key will be passed as the `X-API-KEY` header in every API request. HeyReach does not use OAuth for API authentication, so treat this key with the same security posture as a database credential. If you are integrating HeyReach into a team environment or via Maestro, create a dedicated API key for each integration context so you can rotate or revoke individual keys without disrupting other connections. Test that the key is active by making a GET request to the `/campaigns` endpoint before proceeding with deeper integration work.

curl -X GET https://api.heyreach.io/api/public/campaign/GetAllCampaigns \
  -H 'X-API-KEY: your_api_key_here' \
  -H 'Content-Type: application/json'

Connect HeyReach to HubSpot via Native Integration

Inside HeyReach, navigate to Integrations > HubSpot and click 'Connect.' You will be redirected to HubSpot's OAuth authorization flow — make sure you are logged into the HubSpot account you want to sync with before proceeding. Once authorized, return to HeyReach and configure your field mapping: map HeyReach's LinkedIn profile fields (first name, last name, LinkedIn URL, company, job title) to the corresponding HubSpot contact properties. Set your sync triggers — we recommend enabling sync on 'Connection Accepted' and 'Reply Received' as minimum viable triggers. Optionally, enable bi-directional sync so HubSpot contact lists can populate HeyReach lead lists automatically. Verify the connection by accepting a test connection in HeyReach and confirming the contact appears in HubSpot within 2–5 minutes.

Create a Lead List and Add Leads via API

Before launching a campaign, you need a lead list populated with your target prospects. You can create lists manually in the UI, import from CSV, sync from HubSpot, pull from Clay, or create them programmatically via the API. For GTM engineering workflows where lead lists are generated dynamically (e.g., from intent data or CRM triggers), use the POST `/lists` endpoint to create a named list, then use POST `/leads` to add individual leads with their LinkedIn profile URLs and any custom personalization variables. Custom variables you define here become available as merge tags in your campaign message sequences — this is how Clay-enriched data flows into personalized HeyReach messages.

// Create a lead list
curl -X POST https://api.heyreach.io/api/public/list/CreateEmptyList \
  -H 'X-API-KEY: your_api_key_here' \
  -H 'Content-Type: application/json' \
  -d '{"name": "Intent Signals - Week 23"}'

// Add a lead to a list
curl -X POST https://api.heyreach.io/api/public/lead/AddLeadToList \
  -H 'X-API-KEY: your_api_key_here' \
  -H 'Content-Type: application/json' \
  -d '{
    "listId": "your_list_id",
    "profileUrl": "https://linkedin.com/in/prospect-profile",
    "firstName": "Jane",
    "lastName": "Smith",
    "customVariables": {"company_tech_stack": "Salesforce, Outreach"}
  }'

Set Up a Zapier Workflow for Real-Time Reply Alerts

In Zapier, create a new Zap with HeyReach as the trigger app. Select 'New Reply Received' as the trigger event and authenticate with your HeyReach account. Test the trigger to confirm Zapier can pull sample reply data. For the action step, add Slack (or Microsoft Teams) and configure it to send a formatted message to your #linkedin-replies channel — include the prospect's name, their message, campaign name, and a direct link to their LinkedIn profile. This workflow ensures your SDRs see hot replies within seconds rather than checking HeyReach manually throughout the day. Add an optional filter step before the Slack action to only route replies that contain positive sentiment indicators.

Configure the Clay-to-HeyReach Enrichment Loop

In Clay, build a table that sources leads from your ICP (via LinkedIn scrape, CSV import, or CRM sync) and run enrichment waterfalls — pulling firmographic data, technographic data, contact info, and recent job change signals from Clay's provider network. Once enrichment is complete, add a Clay action column using the HeyReach integration: select 'Add Lead to Campaign,' authenticate with your HeyReach API key, and map Clay column values to HeyReach lead fields including custom personalization variables. Set a filter condition so only leads meeting your quality threshold (e.g., work email found + company size 50–500 + uses target tech stack) are pushed to HeyReach. This loop ensures HeyReach campaigns only contain pre-qualified, enriched leads — dramatically improving acceptance and reply rates.

Pull Campaign Analytics via API into Your Reporting Stack

Use the HeyReach analytics endpoint to pull campaign performance data into your reporting infrastructure on a scheduled basis. This is particularly valuable for agencies producing client reports and for GTM engineers building closed-loop optimization workflows where underperforming campaigns are automatically paused or message variants are rotated based on reply rate thresholds. Schedule the API pull via a cron job, a Zapier Schedule trigger, or a Clay scheduled table refresh. Push the data to Google Sheets, a SQL database, or a BI tool like Looker. Combine HeyReach analytics with Instantly email metrics and HubSpot pipeline data for a unified multichannel outbound dashboard.

curl -X GET 'https://api.heyreach.io/api/public/campaign/GetCampaignAnalytics?campaignId=your_campaign_id' \
  -H 'X-API-KEY: your_api_key_here' \
  -H 'Content-Type: application/json'