Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Tags" resource to create a new tag rule. It is designed to send a request that includes user identification and tag data, allowing users to programmatically define tagging rules within an external system. This can be useful in scenarios where automated categorization or labeling of items based on dynamic criteria is needed, such as organizing content, managing metadata, or applying labels for workflow automation.

For example, a user might use this node to create a rule that automatically tags incoming documents with specific keywords or categories based on their content or origin.

Properties

Name Meaning
X USER ID The User Id header value used to identify the user making the request.
Data JSON object containing the tag rule details. Expected to include a tags array string.
  • X USER ID is required and sent as a header named X-USER-ID.
  • Data is a JSON input representing the body of the request, typically including a tags property which should be an array (as a string) specifying the tags to apply.

Output

The node outputs JSON data corresponding to the response from the API after creating the tag rule. The exact structure depends on the external service's response but generally will confirm the creation status and may include details of the created tag rule.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external Connect Secure API.
  • The node uses an OpenAPI specification internally to build its properties and handle requests.
  • Proper configuration of the API credentials in n8n is necessary for successful operation.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • Malformed JSON in Data property: The data field must be valid JSON. Errors parsing this will cause the request to fail.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • API response errors: If the external API returns errors, check the message for clues (e.g., invalid tags format, permission issues).

Links and References

  • No direct links are included in the source code, but users should refer to the external Connect Secure API documentation for detailed information on tag rule creation and expected request/response formats.

Discussion