Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ciphers View under the Asset Data resource, is designed to fetch cipher-related data from the Connect Secure API. It allows users to query and retrieve specific cipher information based on conditions, pagination, and sorting preferences.

Typical use cases include:

  • Extracting filtered cipher data for security audits.
  • Retrieving subsets of cipher records for reporting or analysis.
  • Sorting cipher data by specified fields to prioritize or organize results.

For example, a user might want to retrieve all ciphers matching a certain condition (e.g., ciphers created after a specific date), skip the first 10 records, limit the output to 50 records, and order them by creation date.

Properties

Name Meaning
X USER ID User identifier required in the request header to authenticate or identify the user.
Condition Query condition string to filter the cipher data returned by the API.
Skip Number of records to skip (offset) for pagination purposes.
Limit Maximum number of records to return (limit) for pagination.
Order By Field name(s) to order the returned cipher data by, e.g., "created_at desc".

Output

The node outputs JSON data representing the retrieved cipher records matching the query parameters. The structure typically includes an array of cipher objects with their respective properties as defined by the Connect Secure API's response schema.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The X USER ID header must be provided as part of the input properties to identify the user context for the API call.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid query condition syntax: If the condition string is malformed, the API might return errors or no data. Validate the query condition format according to the API documentation.
  • Pagination issues: Setting skip or limit incorrectly (e.g., negative numbers) could cause unexpected results or errors.
  • Order By field not recognized: Using unsupported fields in the order_by parameter may result in API errors or default ordering.
  • Authentication failures: Verify that the API credentials are correctly configured and have sufficient permissions.

Links and References

Discussion