AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node integrates with the AvantGuard ConnectSecure API to retrieve company data. Specifically, the "Get Retrieve Companies" operation fetches a list of companies based on optional query parameters such as filtering conditions, pagination, and sorting. This node is useful in scenarios where you need to synchronize or analyze company information from the AvantGuard system within an n8n workflow.

Practical examples include:

  • Fetching a filtered list of companies matching certain criteria for reporting.
  • Paginating through large sets of company records to process them in batches.
  • Ordering companies by specific fields to prioritize processing.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved companies. Each item in the output corresponds to a company record returned by the API, structured according to the AvantGuard ConnectSecure API's response schema. The output does not include binary data.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI integration.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the "X USER ID" header; ensure it is provided and correct.
  • Invalid query parameters: Incorrect values in additional query parameters like "condition", "skip", "limit", or "order_by" may cause API errors. Validate these before running.
  • Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Network issues: Ensure the base URL is reachable from the n8n environment.

Links and References

Discussion