AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves detailed information about jobs from an external service. It is useful when you need to fetch specific job records, possibly filtered or sorted according to certain criteria. Typical use cases include monitoring job statuses, auditing job executions, or integrating job data into workflows for further processing.

For example, you might use this node to:

  • Get details of all jobs assigned to a particular user.
  • Retrieve a subset of jobs based on conditions like date ranges or status.
  • Order the retrieved jobs by creation date or priority.

Properties

Name Meaning
X USER ID The User Id header value required to identify the user making the 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 output contains a JSON object with the retrieved job details. Each item in the output corresponds to a job record matching the query parameters. The structure typically includes fields describing the job's attributes such as ID, status, timestamps, and other metadata provided by the external service.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node sends HTTP requests with headers including X-USER-ID and expects JSON responses.

Troubleshooting

  • Missing or invalid X USER ID: The request will fail if the X USER ID header is not provided or incorrect. Ensure this property is set correctly.
  • Invalid query parameters: Providing unsupported or malformed query parameters may cause errors or empty results. Validate the condition syntax and numeric values for skip/limit.
  • Authentication errors: If the API key credential is missing or invalid, the node will not authenticate successfully.
  • Network issues: Connectivity problems to the API endpoint can cause timeouts or failures.

To resolve these issues:

  • Double-check the X USER ID input.
  • Verify the API key credential configuration.
  • Confirm that query parameters conform to expected formats.
  • Ensure network access to the API base URL.

Links and References

  • Refer to the external service’s API documentation for details on supported query parameters and response schema.
  • n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.

Discussion