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 campaigns, contacts, tags, opt-ins, and more. Specifically, for the Tag - Update operation, it enables updating existing tags by changing their name and/or description. This is useful in scenarios where tag metadata needs to be kept current or corrected, such as renaming a tag to better reflect its purpose or adding descriptive information for clarity.
Practical examples:
- Renaming a marketing tag from "Summer Sale" to "Summer 2024 Sale".
- Adding a description to a tag that categorizes customer interests for better segmentation.
Properties
| Name | Meaning |
|---|---|
| Tag | Select the tag to update. You can choose from a list of existing tags or specify the tag ID directly (numeric only). |
| Additional Fields | Optional fields to update on the tag: |
| - Name | The new name for the tag. |
| - Description | The new description for the tag. |
Output
The node outputs an array of JSON objects representing the updated tag(s). Each object typically contains the updated tag details such as its ID, name, description, and possibly other metadata returned by the 4leads API after the update operation.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the 4leads API via an API key credential configured in n8n.
- The node depends on internal handler modules to perform resource-specific operations, including the
tagHandlerfor tag-related actions. - The node uses helper methods to fetch lists of tags for selection and validation.
Troubleshooting
- Invalid Tag ID: If specifying the tag by ID, ensure it is numeric only; otherwise, a validation error will occur.
- Tag Not Found: Selecting a tag that does not exist or has been deleted may cause errors. Use the provided list mode to select valid tags.
- API Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to update tags.
- Empty Update Fields: If no additional fields are provided to update, the operation might result in no changes or an error depending on the API behavior.
- Network Issues: Connectivity problems with the 4leads API will cause execution failures; verify network access and API endpoint availability.
Links and References
- 4leads Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General API usage best practices for RESTful services