HeyReach API icon

HeyReach API

Interact with HeyReach API
Join our community

Actions33

Overview

The "Replace Tags" operation for the Lead resource in this node allows users to replace all existing tags on a specified lead with a new list of tags. This is useful when you want to update or standardize the tagging of leads in your system, ensuring that only the specified tags remain associated with the lead.

Common scenarios include:

  • Cleaning up outdated or irrelevant tags on leads.
  • Synchronizing lead tags from another system or source.
  • Bulk updating lead tags during marketing campaigns or sales processes.

For example, if a lead was previously tagged with "prospect" and "interested," but you want to replace those with "qualified" and "priority," this operation will remove the old tags and set the new ones accordingly.

Properties

Name Meaning
Tags List of tags to add for the lead. Multiple tag strings can be provided.
Create Tag If Not Existing Whether to create tags that don't exist in the system. If set to false (default), the operation will fail with an error if any tag does not already exist. If true, missing tags will be created automatically.
Additional Fields Optional additional fields to identify the lead:
• Lead LinkedIn ID: The LinkedIn ID of the lead (optional if Profile URL is provided).
• Profile URL: Full LinkedIn profile URL of the lead (e.g., https://www.linkedin.com/in/john-doe-123456789/).

Output

The output JSON contains the updated lead data after replacing the tags. This typically includes the lead's identifiers and the current list of tags now associated with the lead. The exact structure depends on the API response but generally confirms the successful replacement of tags.

This node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the HeyReach API.
  • The node communicates with the HeyReach API endpoint at https://api.heyreach.io/api/n8n.
  • Proper configuration of the HeyReach API credentials within n8n is necessary.

Troubleshooting

  • Error: Bad Request due to non-existing tags
    If "Create Tag If Not Existing" is set to false and one or more tags do not exist in the system, the API will return a Bad Request error. To resolve this, either enable the option to create tags automatically or ensure all tags exist beforehand.

  • Lead identification issues
    If neither a valid LinkedIn ID nor a Profile URL is provided in the additional fields, the node may fail to identify the lead correctly. Make sure to provide at least one of these identifiers.

  • Authentication errors
    Ensure that the API key credential is correctly configured and has sufficient permissions to modify lead tags.

Links and References

Discussion