Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve information about Backup Software. Specifically, the "Retrieve Backup Software" operation fetches backup software records based on user-defined query parameters such as filtering conditions, pagination controls, and sorting preferences.

Typical use cases include:

  • Fetching a list of backup software entries for a specific user.
  • Querying backup software data with custom filters (e.g., by status or date).
  • Paginating through large sets of backup software records.
  • Sorting results according to specified fields.

For example, a user might want to retrieve all backup software entries created after a certain date, skip the first 10 records, limit the output to 20 records, and order them by creation date descending.

Properties

Name Meaning
X USER ID User Id — a required string header used to identify the user making the request.
Condition Query Condition — a string representing filter criteria to narrow down the results.
Skip Skip No of Records — a number indicating how many records to skip (for pagination).
Limit Limit — a number specifying the maximum number of records to return.
Order By Order By — a string defining the sorting order of the returned records.

Output

The node outputs JSON data containing the retrieved backup software records matching the query parameters. The structure typically includes an array of backup software objects with their respective properties as defined by the Connect Secure API.

If binary data is returned by the API (not indicated in the provided code), it would be included accordingly, but this node primarily deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure service being accessible.
  • Uses the @devlikeapro/n8n-openapi-node package for OpenAPI-based request handling.
  • Requires proper configuration of the API credentials within n8n.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is set correctly.
  • Invalid query condition syntax: If the condition string is malformed, the API may reject the request. Verify the query format matches API expectations.
  • Pagination issues: Setting skip or limit incorrectly may result in empty or incomplete data sets.
  • Authentication errors: Ensure the API key credential is valid and has necessary permissions.
  • Network or API downtime: Connectivity issues with the Connect Secure API will cause failures; check network and service status.

Common error messages likely relate to authentication failures, invalid parameters, or rate limiting by the API.

Links and References

Discussion