HeyReach API icon

HeyReach API

Interact with HeyReach API
Join our community

Actions33

Overview

This node integrates with the HeyReach API to retrieve multiple LinkedIn accounts based on specified criteria. The "Get Many" operation for the LinkedIn Account resource allows users to fetch a list of LinkedIn accounts, supporting pagination and optional keyword filtering. This is useful in scenarios where you want to manage or analyze multiple LinkedIn profiles at once, such as bulk data processing, marketing campaigns, or network analysis.

Practical examples:

  • Fetching the first 50 LinkedIn accounts to display in a dashboard.
  • Searching LinkedIn accounts by a keyword (e.g., company name or user name) to target specific profiles.
  • Paginating through large sets of LinkedIn accounts for batch processing.

Properties

Name Meaning
Offset Number of records to skip for pagination. Defaults to 0.
Limit Maximum number of records to return. Minimum 1, maximum 100. Defaults to 10.
Additional Fields Optional fields to refine the query:
- Keyword A search keyword to filter LinkedIn accounts by name or other relevant fields.

Output

The output contains a JSON array of LinkedIn account objects matching the query parameters. Each object represents a LinkedIn account with its associated details as provided by the HeyReach API.

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

Dependencies

  • Requires an active connection to the HeyReach API via an API key credential.
  • The node expects the HeyReach API base URL https://api.heyreach.io/api/n8n.
  • Proper API authentication credentials must be configured in n8n for this node to function.

Troubleshooting

  • Common issues:

    • Pagination errors if offset or limit values are out of range.
    • Empty results if the keyword filter does not match any LinkedIn accounts.
    • Authentication failures if the API key is missing or invalid.

  • Error messages:

    • Unauthorized / 401: Check that the API key credential is correctly set up and valid.
    • Bad Request / 400: Verify that offset and limit are within allowed ranges and that the keyword string is properly formatted.
    • Rate limit exceeded: The HeyReach API may limit requests; consider adding delays or reducing request frequency.

Links and References

Discussion