Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve integration credentials. Specifically, for the "Integration" resource and the "Retrieve Integration Credentials" operation, it fetches credential data related to integrations based on user-supplied query parameters and headers.

Typical use cases include:

  • Fetching stored integration credentials for a given user or system.
  • Querying integration credentials with filtering, pagination, and sorting options.
  • Automating workflows that require access to integration authentication details securely.

For example, a user might want to retrieve all integration credentials associated with their user ID, limiting results to 10 entries, skipping the first 5, and ordering them by creation date.

Properties

Name Meaning
X USER ID User Id header value to identify the user making the request.
Condition Query condition string to filter the integration credentials returned.
Skip Number of records to skip (for pagination).
Limit Maximum number of records to return.
Order By Field name(s) to order the results by (e.g., "createdAt", "name").

Output

The node outputs JSON data representing the retrieved integration credentials. The structure typically includes an array of credential objects matching the query conditions, each containing fields relevant to the integration credentials such as IDs, names, and possibly metadata.

No binary data output is indicated in the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • The node uses the OpenAPI specification bundled internally to build its properties and operations.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors.
  • Invalid query parameters: Providing malformed or unsupported values in condition, skip, limit, or order_by may result in API errors or empty responses.
  • API connectivity issues: Network problems or incorrect API credentials can cause failures when attempting to retrieve data.
  • Empty results: If no integration credentials match the query conditions, the output will be empty; verify the correctness of filters and user ID.

Links and References

Discussion