Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation updates a tag rule in the "Tags" resource by sending an HTTP request with specified user identification and tag data. It is useful when you want to modify existing tagging rules programmatically, for example, updating tags associated with certain items or entities in an external system that supports tag rules.

Practical examples include:

  • Updating categorization tags on customer records.
  • Modifying label rules for content management systems.
  • Adjusting metadata tags used for filtering or searching in integrated applications.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Data JSON-formatted string representing the new tag data to update. Example: {"tags": []}
Id Numeric identifier of the tag rule to be updated.

Output

The node outputs JSON data representing the response from the API after attempting to update the tag rule. This typically includes confirmation of the update, the updated tag rule details, or error information if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key or token credential configured in n8n to authenticate requests to the Connect Secure API.
  • Depends on the external Connect Secure API endpoint that manages tag rules.
  • Uses the lodash library internally (bundled) but this does not affect user configuration.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is correctly set.
  • Malformed JSON in Data: The "Data" property must be valid JSON. Invalid JSON will cause parsing errors before sending the request.
  • Invalid Id value: The "Id" must correspond to an existing tag rule; otherwise, the API may return a not found or validation error.
  • API Authentication Errors: If the API key or token is missing or incorrect, the request will fail authorization.
  • Network or API downtime: Temporary connectivity issues or API service outages can cause failures.

To resolve these:

  • Double-check all input properties for correctness.
  • Validate JSON syntax in the "Data" field.
  • Confirm the tag rule ID exists in the target system.
  • Verify API credentials are properly configured in n8n.

Links and References

Discussion