Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Tags" resource of the Connect Secure API, specifically to retrieve a tag rule by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a specific tag rule associated with a user in the Connect Secure system. For example, this node can be used in automation workflows that manage or audit tag rules for users, enabling dynamic retrieval and processing of tag metadata.

Properties

Name Meaning
X USER ID The User Id header value to identify the user context for which the tag rule is retrieved. This is required and passed as an HTTP header X-USER-ID.
Id The numeric identifier of the tag rule to retrieve. This is required and specifies which tag rule to fetch.

Output

The node outputs JSON data representing the details of the requested tag rule. The exact structure depends on the API response but typically includes fields such as the tag rule's id, name, conditions, actions, and other metadata related to the tag rule configuration.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and the provided user ID and tag rule ID being valid.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID: If the user ID header is missing or incorrect, the API may return authorization errors or fail to find the tag rule. Ensure the "X USER ID" property is correctly set.
  • Invalid tag rule Id: Providing an invalid or non-existent tag rule ID will result in an error or empty response. Verify the ID before running the node.
  • API authentication errors: Make sure the API key credential is properly configured and has sufficient permissions.
  • Network or connectivity issues: Confirm that the Connect Secure API endpoint is reachable from your n8n instance.

Common error messages would likely relate to unauthorized access, not found resources, or bad requests due to missing parameters.

Links and References

  • Connect Secure API documentation (refer to official docs for detailed tag rule schema and endpoints)
  • n8n documentation on using API key credentials and HTTP headers in nodes

Discussion