Skip to main content
HeyReach is a LinkedIn automation platform for managing outreach campaigns at scale. The Cargo integration allows you to add leads to campaigns, stop leads, retrieve lead information, and listen to real-time campaign events.

​
Authentication

Connect to HeyReach using your API key.

​
Connection details

FieldDescription
API KeyYour HeyReach API key

​
HeyReach actions

​
Get lead

Retrieve information about a lead by their LinkedIn profile URL. Configuration
FieldDescription
Profile URLLinkedIn profile URL

​
Add lead to campaign

Add a new lead to a HeyReach campaign with full personalization data. Configuration
FieldDescription
CampaignSelect the target campaign
LinkedIn accountLinkedIn account to use for outreach
First nameLead’s first name (required)
Last nameLead’s last name (required)
Profile URLLinkedIn profile URL (required)
LocationLead’s location
SummaryLead’s LinkedIn summary
Company nameCurrent company
PositionCurrent job title
AboutLead’s about section
Email addressLead’s email address
Custom mappingsAdditional custom fields for personalization
Pass as much personalization data as possible to improve campaign engagement rates.

​
Stop lead in campaign

Stop outreach to a lead in a specific campaign. Configuration
FieldDescription
CampaignSelect the campaign
Profile URLLinkedIn profile URL to stop

​
HeyReach extractors

​
Listen events

Listen to real-time HeyReach webhook events and ingest them as contact events. When enabled, Cargo registers webhooks in your HeyReach workspace for every supported event type and automatically ingests each event as it occurs. Cargo reconciles its webhooks on every sync — recreating any that are missing and removing stale or duplicate ones — so the configured set stays in sync with HeyReach. Captured events CONNECTION_REQUEST_SENT, CONNECTION_REQUEST_ACCEPTED, MESSAGE_SENT, MESSAGE_REPLY_RECEIVED, INMAIL_SENT, INMAIL_REPLY_RECEIVED, FOLLOW_SENT, LIKED_POST, VIEWED_PROFILE, CAMPAIGN_COMPLETED, and LEAD_TAG_UPDATED. Output fields Every event is mapped to a fixed, predictable set of columns. The nested lead, campaign, and sender objects are flattened to the top level with a prefix — for example lead.profile_url becomes lead_profile_url and campaign.name becomes campaign_name. Fields that only apply to certain event types (e.g. connection_message, recent_messages, recent_inmails, conversation_id) are left empty when not relevant. Columns include event_type, timestamp, correlation_id, the campaign_*, sender_*, and lead_* fields (such as lead_profile_url, lead_email_address, lead_first_name, lead_last_name, lead_company_name, lead_position, lead_tags, lead_lists), plus the message/conversation fields for messaging events.
Events are unified as contact events, matched on the lead’s LinkedIn profile URL and, when present, their email address.

​
Use cases

Add leads that meet your ICP criteria to targeted LinkedIn campaigns.
Combine LinkedIn outreach with email for multi-touch campaigns.
Dynamically add or stop leads based on their engagement or status changes.

​
Best practices

  1. Validate LinkedIn URLs - Ensure profile URLs are valid before adding to campaigns
  2. Use custom mappings - Pass personalization variables for better response rates
  3. Monitor campaign limits - Respect LinkedIn’s daily connection and message limits