Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
This node integrates with the 4leads platform, allowing users to manage various resources such as contacts, tags, campaigns, and more. Specifically, for the Contact resource with the Add a Tag operation, it enables adding one or multiple tags to a selected contact in 4leads.
Common scenarios include:
- Organizing contacts by tagging them based on behavior, preferences, or campaign responses.
- Automating marketing workflows where contacts are tagged dynamically.
- Segmenting contacts for targeted communication.
For example, you might use this node to add a "VIP" tag to contacts who made a purchase, or add multiple tags like "Newsletter Subscriber" and "Event Attendee" to a contact at once.
Properties
| Name | Meaning |
|---|---|
| Contact | Select the contact to which you want to add tags. You can choose from a list of contacts or specify the contact ID directly. |
| Edit a List of Tags | Boolean toggle to decide whether to add a single tag or multiple tags at once. |
| Tag | When adding a single tag, select the tag from a list or specify its ID. |
| Tag Names or IDs | When adding multiple tags, select one or more tags from the list or specify their IDs using expressions. |
| The email of a contact can be used as an alternative ID. | Notice informing that the contact's email can be used as an alternative identifier in some operations (not directly editable). |
Output
The node outputs a JSON array containing the results of the tag addition operation(s). Each item in the output corresponds to the response from the 4leads API for the processed contact-tag association.
If binary data were involved (not indicated here), it would typically represent files or media related to the contact or tag, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the 4leads API via an API key credential configured in n8n.
- Uses internal helper methods to fetch lists of contacts and tags for selection.
- No additional external dependencies beyond the 4leads API.
Troubleshooting
Common issues:
- Selecting a contact or tag that does not exist or is inaccessible due to permissions may cause errors.
- Providing invalid tag IDs (non-numeric) will fail validation.
- Network or authentication failures with the 4leads API will prevent successful execution.
Error messages:
- Validation error: "Not a valid tag ID" — occurs if the tag ID format is incorrect; ensure numeric IDs are used.
- API errors related to missing or invalid credentials — verify the API key is correctly set up in n8n.
- Contact or tag not found errors — confirm the selected contact and tag exist in your 4leads account.
Links and References
- 4leads API Documentation (hypothetical link)
- n8n Expressions Documentation — for using expressions to specify tag IDs dynamically.