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 to retrieve information about tags. Specifically, the "Get" operation under the "Tag" resource allows users to either fetch a single tag by its ID or search for multiple tags based on criteria such as search string, page size, and page number.
Common scenarios where this node is beneficial include:
- Retrieving detailed information about a specific tag to use in further workflow steps.
- Searching and listing tags that match certain text criteria, useful for filtering or reporting purposes.
- Paginating through large sets of tags when dealing with many entries.
For example, you might use this node to get details of a particular marketing tag applied to contacts or to list all tags containing a certain keyword to analyze tagging trends.
Properties
| Name | Meaning |
|---|---|
| Search for multiple results (bReturnAll) | Boolean flag to choose between returning a single tag object (false) or a list of tag objects (true). |
| Tag (tagId) | When fetching a single tag (bReturnAll is false), select the tag either from a searchable list or specify its numeric ID directly. |
| Additional Fields (tagQs) | When fetching multiple tags (bReturnAll is true), optional parameters to refine the search: • Search String: Text to search within tag names. • Page Size: Number of results per page (e.g., 5, 10, 20, 50, 200). • Page Number: The page index to retrieve (1-based). |
Output
The node outputs JSON data representing one or more tag objects retrieved from the 4leads platform.
- If fetching a single tag, the output is a JSON object with the tag's details.
- If fetching multiple tags, the output is an array of tag objects matching the search criteria and pagination settings.
The exact structure of each tag object depends on the 4leads API but typically includes fields like tag ID, name, and other metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the 4leads API via an API key credential configured in n8n.
- The node relies on internal handler functions to communicate with the 4leads service.
- Proper network access to the 4leads API endpoint is necessary.
Troubleshooting
- Invalid Tag ID Error: If specifying a tag ID manually, ensure it consists only of digits; otherwise, a validation error will occur.
- Empty Results When Searching: Check that the search string is correctly specified and that page size and number are valid integers.
- API Authentication Failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- Pagination Issues: If requesting pages beyond available data, the result may be empty; adjust page number accordingly.
- Network Errors: Ensure your environment can reach the 4leads API endpoints without firewall or proxy issues.
Links and References
- 4leads Official Documentation (for API details and tag object schema)
- n8n Documentation on Creating Custom Nodes