Actions30
- 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 various types of data. Specifically, for the Other Data resource and the Get BAG Data operation, it fetches Dutch BAG (Basisregistratie Adressen en Gebouwen) data based on a given address. This is useful for workflows that need detailed address information from the official Dutch BAG registry, such as verifying addresses, enriching customer data, or integrating property-related information into business processes.
Practical examples include:
- Validating and standardizing Dutch addresses in CRM systems.
- Enriching lead or customer records with official building and address data.
- Automating property-related workflows that require accurate location details.
Properties
| Name | Meaning |
|---|---|
| Postcode | (Required) The postal code of the address to query. |
| House Number | (Required) The house number of the address to query. |
| Suffix | (Optional) A suffix to the house number, such as "2" or "A". |
Output
The node outputs JSON data containing the response from the Bedrijfsdata API's /bag endpoint. This JSON typically includes detailed BAG data about the specified address, such as building identifiers, address components, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires an API key credential configured in n8n for authenticating requests to the Bedrijfsdata service.
- The base URL used for requests is
https://api.bedrijfsdata.nl/v1.2.
Troubleshooting
- Missing or invalid postcode/house number: Since these are required fields, ensure they are provided and correctly formatted. Missing these will likely cause the API request to fail.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Unexpected API responses: If the API returns errors or unexpected data, check the validity of the input parameters and consult the Bedrijfsdata API documentation for any changes or limitations.
- Network issues: Ensure that the n8n instance can reach the Bedrijfsdata API endpoint without firewall or proxy restrictions.
Links and References
- Bedrijfsdata API Documentation (official API docs for more details on endpoints and data)
- Dutch BAG Registry Information (background on the BAG dataset)