HeyReach API icon

HeyReach API

Interact with HeyReach API

Overview

The "Get Many For Lead" operation under the Campaign resource retrieves multiple campaign records associated with a specific lead in HeyReach. This node is useful when you want to fetch campaigns linked to a particular LinkedIn lead, enabling you to analyze or process campaign data relevant to that lead.

Practical scenarios include:

  • Fetching all campaigns targeting a specific LinkedIn profile for reporting.
  • Retrieving campaigns filtered by email or LinkedIn ID of a lead to tailor marketing strategies.
  • Paginating through large sets of campaign data related to a lead for batch processing.

Properties

Name Meaning
Offset Number of records to skip for pagination. Defaults to 0.
Limit Maximum number of records to return. Maximum allowed is 100. Defaults to 10.
Profile URL The full LinkedIn profile URL of the lead. Must follow the format: 'https://www.linkedin.com/in/username/'. Leave empty if not filtering by profile URL.
Email (Additional Field) The email address of the lead. Leave empty if not filtering by email.
LinkedIn ID (Additional Field) The LinkedIn ID of the lead. Can be obtained from other API responses. Leave empty if not filtering by LinkedIn ID.

Output

The node outputs JSON data containing an array of campaign objects associated with the specified lead. Each campaign object includes details as defined by the HeyReach API's campaign schema. The output structure allows further processing or integration within n8n workflows.

If binary data were involved (not indicated here), it would typically represent files or media related to campaigns, but this operation focuses on JSON campaign data only.

Dependencies

  • Requires an active connection to the HeyReach API.
  • An API key credential must be configured in n8n to authenticate requests to HeyReach.
  • Network access to https://api.heyreach.io/api/n8n is necessary.

Troubleshooting

  • Invalid Profile URL Format: Ensure the LinkedIn profile URL strictly follows the format https://www.linkedin.com/in/username/. Incorrect formats may cause the API to reject the request.
  • Pagination Limits: Setting limit above 100 will likely result in an error; keep it at or below 100.
  • Empty Filters: If no filters (Profile URL, Email, LinkedIn ID) are provided, the API might return no results or an error depending on backend validation.
  • Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Network Issues: Check connectivity to the HeyReach API endpoint if requests time out or fail.

Links and References

Discussion