Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve Suid permissions related to assets. It is designed to fetch permission data for a specific user, filtered and sorted according to various query parameters. This node is useful in scenarios where you need to programmatically access or audit user permissions on assets within an enterprise system, such as generating reports on user access rights or integrating permission checks into automated workflows.

Practical examples include:

  • Retrieving all Suid permissions for a given user to verify their access levels.
  • Filtering permissions based on specific conditions (e.g., asset type or status).
  • Paginating results by skipping a number of records and limiting the output size.
  • Ordering the retrieved permissions by specified fields.

Properties

Name Meaning
X USER ID The User Id for whom Suid permissions are being retrieved. This is sent as a request header.
Condition A query string condition to filter the Suid permissions returned by the API.
Skip Number of records to skip in the result set, used for pagination.
Limit Maximum number of records to return, used to limit the size of the response.
Order By Field(s) by which to order the returned Suid permissions.

Output

The node outputs JSON data representing the Suid permissions retrieved from the Connect Secure API. Each item in the output corresponds to a permission record associated with the specified user and filtered according to the input properties.

If binary data were involved, it would typically represent files or attachments related to permissions, but this node focuses solely on JSON permission data.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API service being accessible.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid query parameters: Conditions, skip, limit, and order_by must conform to the API's expected formats; incorrect values may cause errors or empty responses.
  • Network issues: Connectivity problems to the Connect Secure API will prevent data retrieval; check network settings and API endpoint availability.

Common error messages might include unauthorized access, bad request due to malformed query parameters, or timeout errors. Resolving these involves checking credentials, validating input parameters, and ensuring stable network connectivity.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed usage)
  • n8n documentation on HTTP Request nodes and API integrations for general guidance

Discussion