Actions31
- Company Actions
- Company (Related) Actions
- Data (Advanced) Actions
- Enrich Actions
- Live Web RAG Actions
- LLM Template Actions
- Other Data Actions
- Validation & Cleansing Actions
Overview
This node interacts with the Bedrijfsdata API to retrieve multiple job vacancies for a specified company. It is designed to fetch vacancy listings based on a company's unique identifier and optionally filter these vacancies using a search query. The node can also provide detailed metadata about the vacancies retrieval, such as total count and credit usage.
Common scenarios where this node is beneficial:
- HR teams or recruiters wanting to automate fetching current job openings from a specific company.
- Business intelligence workflows that monitor competitor hiring activity.
- Job boards or aggregators pulling vacancy data directly from company profiles.
- Automated reporting on recruitment trends within a company.
Practical example:
A recruiter sets up an automation to pull all open vacancies from a target company by providing its Bedrijfsdata.nl ID. They optionally add a keyword search (e.g., "engineer") to narrow down results. The node returns a list of matching vacancies, which can then be processed further or sent via email.
Properties
| Name | Meaning |
|---|---|
| Bedrijfsdata.nl ID | (Required) The unique identifier of the company in the Bedrijfsdata.nl system for which vacancies are retrieved. |
| Search Query | (Optional) A text string to filter vacancies by keywords or phrases, allowing targeted vacancy searches. |
| Detailed Output | (Boolean) If enabled, returns detailed metadata such as total number of vacancies found and credit usage. Note: When enabled, output is a single item instead of an array of vacancies. |
Output
The node outputs JSON data representing the vacancies retrieved from the Bedrijfsdata API:
- Default output: An array of vacancy objects, each describing a single job opening associated with the specified company.
- When Detailed Output is enabled: A single JSON object containing additional metadata fields like total vacancies found and credit usage statistics instead of the vacancy list.
The exact structure of each vacancy object depends on the API response but typically includes fields such as job title, description, location, and posting date.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Needs an API authentication token configured in n8n credentials (referred generically as an API key credential).
- Internet access to reach
https://api.bedrijfsdata.nl/v1.2.
Troubleshooting
- Missing or invalid Bedrijfsdata.nl ID: The node requires a valid company ID; ensure this is correctly provided. Errors will occur if the ID is missing or incorrect.
- Empty or no vacancies returned: If the search query filters too strictly or the company has no current vacancies, the result may be empty.
- API rate limits or quota exceeded: The API may limit requests or credits; enabling detailed output helps monitor credit usage.
- Network or authentication errors: Verify API credentials and network connectivity to the Bedrijfsdata API endpoint.
- Unexpected API responses: If the API changes or returns unexpected data, the node may throw errors indicating failure to parse or process the response.
Links and References
- Bedrijfsdata API Documentation (official API docs)
- n8n Documentation - Creating Custom Nodes
- Job Vacancy Data Use Cases (general reference on job data integration)
If you need details on other operations or resources, feel free to ask!