Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Company" resource to retrieve a view of jobs data. It is designed to query job listings or job-related information from an external API, allowing users to filter, paginate, and order the results. This node is useful in scenarios where you want to integrate job data into your workflows, such as displaying job openings on a website, syncing job data with other systems, or automating job-related notifications.

Practical examples:

  • Fetching a filtered list of jobs based on specific conditions (e.g., location, department).
  • Paginating through large sets of job records by skipping and limiting the number of results.
  • Ordering job listings by date posted or relevance.

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 the jobs data returned by the API.
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field name(s) to order the results by (e.g., date, relevance).

Output

The node outputs JSON data representing the retrieved jobs view. The structure typically includes an array of job objects matching the query parameters. Each job object contains fields relevant to the job listing, such as job title, description, location, and other metadata as provided by the API.

If the API supports binary data (not indicated here), it would be summarized accordingly, but this node primarily returns structured JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • Depends on the external Connect Secure API service to fetch company job data.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is set correctly.
  • Invalid query conditions: Malformed or unsupported query strings may cause errors or empty results.
  • Pagination issues: Setting skip or limit incorrectly might result in no data or repeated data.
  • API authentication errors: Verify that the API key credential is configured properly in n8n.
  • Network or connectivity problems: Ensure the n8n instance can reach the external API endpoint.

Common error messages will likely relate to authentication failures, invalid query parameters, or rate limiting by the API provider. Checking the API documentation and logs can help resolve these.

Links and References

Discussion