Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
The node provides functionality to interact with "Tags" in an external system, specifically allowing users to retrieve details of a single tag by its identifier. This operation is useful when you want to fetch metadata or properties related to a specific tag, for example, to use that information in subsequent workflow steps such as filtering contacts, segmenting data, or triggering conditional logic based on tag attributes.
A practical example would be: In a marketing automation workflow, after tagging a contact based on their behavior, you might want to get the full details of that tag to decide what personalized content to send next.
Properties
| Name | Meaning |
|---|---|
| Tag | Choose a tag from a dynamically loaded list of available tags or specify a tag ID manually using an expression. This identifies which tag's details will be retrieved. |
Output
The output of this node includes a JSON object representing the details of the requested tag. The structure typically contains fields describing the tag's properties such as its ID, name, and possibly other metadata depending on the external system's API response.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is expected to be purely JSON-based.
Dependencies
- The node depends on external methods defined in a separate
methodsmodule, particularly for loading options (e.g., fetching the list of tags). - It uses a router function from an
actions/routermodule to handle execution flow. - Requires configuration of an API key or authentication token to connect to the external service managing tags.
- The dynamic loading of tag options suggests the need for network connectivity and proper credentials configured within n8n.
Troubleshooting
Common issues:
- Failure to load tag options could occur if the API credentials are missing or invalid.
- Specifying an incorrect or non-existent tag ID may result in errors or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors related to authentication usually indicate misconfigured or expired API keys; verify and update credentials.
- "Tag not found" or similar errors suggest the specified tag ID does not exist; double-check the ID or select from the dropdown.
- Timeout or connection errors imply network issues; ensure the external service is reachable.
Links and References
- n8n Expressions Documentation — for guidance on specifying tag IDs dynamically.
- External API documentation for the tag management system (not provided here) would be helpful to understand the exact structure of tag data returned.