4leads icon

4leads

Interact with 4leads

Actions33

Overview

This node integrates with the 4leads platform, allowing users to perform various operations on different resources such as Campaigns, Contacts, Tags, Opt-Ins, and more. Specifically, for the Tag resource with the Delete operation, the node enables users to delete a tag from their 4leads account.

Common scenarios where this node is beneficial include:

  • Cleaning up unused or obsolete tags in your marketing automation system.
  • Managing tag lifecycle programmatically as part of data hygiene workflows.
  • Automating tag removal based on external triggers or conditions.

For example, you might use this node to automatically delete tags that are no longer associated with any active campaigns or contacts, helping keep your tagging system organized.

Properties

Name Meaning
Tag Select the tag to delete. You can either choose from a searchable list of existing tags or specify the tag ID directly (must be numeric).

The "Tag" property supports two modes:

  • From List: Search and select a tag by name from the available tags.
  • By ID: Enter the numeric ID of the tag to delete.

Output

The node outputs a JSON array containing the results of the delete operation(s). Each item in the output corresponds to the response from deleting a tag. The exact structure depends on the 4leads API response but typically includes confirmation of deletion or relevant metadata.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the 4leads API via an API key credential configured in n8n.
  • The node depends on internal handler modules that interact with the 4leads API endpoints for tags.
  • Proper permissions on the 4leads account to delete tags are necessary.

Troubleshooting

  • Invalid Tag ID: If you enter a non-numeric tag ID, the node will reject it due to validation rules. Ensure the tag ID consists only of digits.
  • Tag Not Found: Attempting to delete a tag that does not exist or has already been deleted may result in an error from the API. Verify the tag exists before deletion.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key credential is correctly set up and has sufficient permissions.
  • API Rate Limits: Frequent delete operations might hit API rate limits. Implement retry logic or reduce request frequency if errors occur.
  • Network Issues: Connectivity problems between n8n and the 4leads API can cause timeouts or failures. Check network status and proxy settings if applicable.

Links and References

Discussion