Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve stored credentials based on specified query parameters. It is useful in scenarios where you need to programmatically fetch credential records filtered by conditions, control pagination, and sort results. For example, you might use this node to list user credentials that meet certain criteria or to integrate credential data retrieval into an automated workflow.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter which credentials to retrieve (e.g., a search filter).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of records to return.
Order By Field name(s) to order the returned credentials by (e.g., "createdAt DESC").

Output

The node outputs JSON data containing the retrieved credentials matching the query parameters. The structure typically includes an array of credential objects with their associated fields as returned by the Connect Secure API. There is no indication that binary data is output by this node.

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 credential.

Troubleshooting

  • Common issues:
    • Missing or invalid API authentication token can cause authorization errors.
    • Incorrect or malformed query conditions may result in empty responses or API errors.
    • Pagination parameters (skip and limit) set incorrectly could lead to unexpected subsets of data.
  • Error messages:
    • Authorization failures usually indicate problems with the provided API key or user ID header.
    • API response errors related to query syntax suggest reviewing the Condition property format.
  • Resolution tips:
    • Verify the API key credential is correctly configured and valid.
    • Ensure the X USER ID header is correctly set and corresponds to a valid user.
    • Test query conditions directly against the API if possible to confirm correctness.

Links and References

Discussion