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 perform various operations on different resources such as contacts, tags, campaigns, opt-ins, and more. Specifically, for the Contact resource and the Get Tag List operation, the node retrieves the list of tags associated with a specified contact. This is useful in scenarios where you want to analyze or manage the tags assigned to contacts for segmentation, marketing automation, or personalized communication.
Practical examples include:
- Fetching all tags linked to a particular contact to understand their interests or status.
- Using the tag list to trigger conditional workflows based on contact segmentation.
- Auditing contact tagging to maintain data hygiene.
Properties
| Name | Meaning |
|---|---|
| Contact | Select the contact whose tag list you want to retrieve. You can choose a contact from a searchable list or specify by ID. |
Note: The provided properties JSON includes a notice about using the email of a contact as an alternative ID, but this applies to other operations and not specifically to "Get Tag List".
Output
The output is a JSON array where each item represents a tag associated with the specified contact. Each tag object typically contains details such as the tag's name and identifier. This structured output allows further processing or filtering within n8n workflows.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but for this operation, the output is purely JSON-based.
Dependencies
- Requires an active connection to the 4leads API via an API key credential configured in n8n.
- The node depends on internal handlers that communicate with 4leads endpoints to fetch contact and tag information.
- No additional external services are required beyond the 4leads API.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a non-existent contact ID will result in errors or empty tag lists.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Contact not found" or similar messages suggest the contact ID does not exist; confirm the contact selection.
- Timeout or network errors require checking internet connectivity or 4leads service status.
Links and References
- 4leads Official Documentation (for API details and authentication)
- n8n Documentation on Creating Custom Nodes