Bedrijfsdata n8n integrationAutomate Bedrijfsdata with n8n.

Retrieves a single company profile from its Bedrijfsdata.nl identifier. This is the read you run once you already know which company you are looking at.

• Bedrijfsdata.nl ID: the identifier of a specific company, required, usually passed from an earlier step as {{ $json.id }}.
• Detailed Output: adds details such as credit usage, and produces output that has to be parsed before you can process the company.

Searches company profiles with filtering, and returns the matches as items. This is the list building operation of the node.

• Country: required, and The Netherlands (nl) is the value on offer.
• Basic Filters: search by attributes such as name, employees or organization type.
• Location Filters: narrow the search down to a registration address.
• Pagination Options: set how the result pages are walked when the search is wider than one page.
• Results Breakdown: adds a count of results per category, province or revenue range among them.

Returns the valid filter values behind the text, apps, city and domain fields used by Get Companies. It answers the question of what to type before a search runs.

• Suggestion Type: required, one of Keywords (Text), Technology (Apps), City (NL only) or Domain Names.
• Search Query: required, and the first two to four letters usually return relevant suggestions.
• Output as Individual Items: splits the suggestions into separate items instead of one.

Lists the companies that belong to the same corporate family as the company you point at. Holdings, subsidiaries and sister entities come back together.

• Bedrijfsdata.nl ID: required, the company whose family you want.
• Max. Number of Results: caps how many company profiles come back.
• Detailed Output: adds the total number of companies found and credit usage, and returns one item instead of an array.

Finds every company registered at the same address as a given one. Shared offices, business centers and letterbox registrations surface here.

• Bedrijfsdata.nl ID: required, the company whose address is used as the anchor.
• Max. Number of Results: limits the number of neighbours returned.
• Detailed Output: reports the total found and the credit usage as a single item.

Returns the employees known for one company. The output feeds contact research rather than a bulk export.

• Bedrijfsdata.nl ID: required, the company whose employees you retrieve.
• Search Query: filters the result, and the documentation asks you to be as specific as GDPR compliance demands in your use case.
• Detailed Output: adds the total number of people found and credit usage, returning a single item.

Pulls news items about a company. Since the node has no trigger, a Schedule step decides how often this runs.

• Bedrijfsdata.nl ID: required, the company you want news items for.
• Search Query: narrows the news down to a specific subject.
• Detailed Output: returns the total number of news items found and credit usage as one item.

Retrieves the job openings published by a company. Hiring is a usable signal of budget and direction.

• Bedrijfsdata.nl ID: required, the company whose vacancies you retrieve.
• Search Query: keeps only the vacancies matching a term, a job family for instance.
• Detailed Output: adds the total number of vacancies found and credit usage, as a single item.

Matches the company data you already hold against the Dutch dataset and returns the enriched profile. Partial input is the normal case here.

• Country: required, The Netherlands (nl).
• Company Name and City: the two fields a messy form usually gives you.
• URL, Email Address and LinkedIn URL: web identifiers that often match more precisely than a name.
• Detailed Output: adds credit usage and produces output that has to be parsed to reach individual companies.

Fetches the content of a publicly accessible website from its domain. The text comes back ready to hand to a model or a summarizer.

• Domain Name: required, the domain of the website to retrieve.

Retrieves one publicly accessible page rather than a whole site, with control over the format that comes back.

• URL: required, the exact page to retrieve.
• Output Options: the collection where the returned formats are configured.
• Localization Options: sets the country and language to browse from, and can add cleaned HTML, Markdown, raw content or a maximum snippet length.

Runs a query against popular search engines and returns the snippets. Useful when you do not know the URL yet.

• Search Query: required, the query to run.
• Search Options: holds the limit on results returned, and a timeout where a low value is quick but skips summaries while a high one gets summaries for pages that load slowly.
• Output Options: chooses what content is attached to each result.

Runs an LLM template you defined on the Bedrijfsdata side and returns the generated content. The template does the retrieval, you pass it a subject.

• Template ID: required, found in your Bedrijfsdata.nl Developers Platform account under LLM templates.
• Provider API Key: required, the key for the model your template uses.
• Provider Endpoint: the model endpoint URL, required depending on the model.
• Template Parameters: feeds the template a company ID, a domain, a search query or a URL.

Returns Dutch BAG data for an address, the national register of buildings and addresses.

• Postcode: required, the postcode of the address.
• House Number: required, and kept separate from the postcode.
• Suffix: the addition to the house number, such as 2 or A, which matters in buildings split into units.

Reads a domain's DNS records directly, straight from the source rather than from a cached profile. It describes the technical setup behind a website, the mail and hosting side of it, rather than the company that owns the name.

• Domain Name: required, the domain to scan.

Queries the European tender database and returns the publications that match your terms. Public sector demand, checked on a schedule instead of by hand, since nothing here pushes a notification to you.

• Search Query: required, the terms used to retrieve EU tenders.

Returns exchange rates for more than 300 currencies, cryptocurrencies included, expressed against the currency you set as the baseline. One call covers every pair you need from that baseline, so a workflow converts a batch of amounts in a single step.

• Currency Code: required, the code used as the baseline for the rates.

Tells you how many times a password has appeared in known leaks. Both parameters are optional, so nothing forces you to send the clear value.

• Password (SHA1): the hashed password, and the recommended way to run the check.
• Password: the clear password, accepted but harder to justify inside a workflow log.

Returns property information, reached either from a company or from an address. Neither input is mandatory, so you choose the entry point.

• Bedrijfsdata.nl ID: searches from a specific company.
• Address ID: searches from a Dutch address in the NL{postcode}-{house number} format, for example NL1234AB-150.

Collects the global rankings held for a domain, Majestic, CRUX, CloudFlare and DomCop among them. Several sources arrive in one response, which saves stitching together a score from separate tools.

• Domain Name: required, the domain whose rankings you retrieve.

Returns data on how a company's website performs and where it ranks in popularity. You can start from the company or from the domain.

• Domain Name: searches by domain name.
• Bedrijfsdata.nl ID: searches by the identifier of a specific company.

Takes an address written in free form and gives it back validated and formatted, so one messy text field turns into usable geographic data. However the person typed it, the response arrives in a predictable shape.

• Geocoding: required, the free form address to resolve, often {{ $json.address }} from the incoming item.
• Country (ISO 3166-1 Alpha-2): optional code such as NL or BE that narrows the lookup to one country.

Checks a BIC number and reports whether it holds up, before it travels any further through a finance workflow. One field in, one verdict out.

• BIC Number: required, the BIC to validate, usually mapped from the banking block of a form with {{ $json.bic }}.

Confirms that a city name is real and hands back the reference form of it. Coverage is global here, not limited to the Netherlands.

• City: required, the city to validate.
• Country (ISO 3166-1 Alpha-2): required, the country code the city belongs to, for example nl or us.

Runs a Dutch VAT number, the btw-nummer, through validation and says whether it is well formed. Only Dutch numbers fall inside this operation.

• Dutch VAT Number: required, the btw-nummer to validate.

Applies a basic validation pass to an email address. The check stays at the format level, so read the result as a signal rather than a deliverability verdict.

• Email Address: required, the address to validate, in the shape name@email.com.

Verifies an IBAN and returns whether the account number stands up to inspection. Worth a step anywhere money is about to move on something a human typed.

• IBAN Number: required, the IBAN to validate.

Examines a Kamer van Koophandel number and signals whether it is valid. That Chamber of Commerce number is the hinge most Dutch B2B records turn on.

• Kamer Van Koophandel (KvK) Number: required, the KvK number to validate.

Assesses a Legal Entity Identifier and states whether it is valid. A broken LEI is hard to spot by eye even though it travels through the whole of financial reporting.

• Legal Entity Identifiers (LEI) Number: required, the LEI to validate.

Validates phone numbers worldwide and tells you whether the one supplied is usable. Naming the country removes the ambiguity when a number carries no international prefix.

• Phone Number: required, the number to validate.
• Country (ISO 3166-1 Alpha-2): optional code such as nl or us that says which numbering plan to assume.

Weighs a postcode against the format its country actually uses and returns the outcome. The coverage is global, so this is not a Dutch only check.

• Postcode: required, the postcode to validate.
• Country (ISO 3166-1 Alpha-2): required, the country code the postcode belongs to, for example nl or us.

Tests a URL and reports whether it holds together, before a broken address is stored, shared or clicked. It is a quick guard on any field where someone was free to paste whatever they had to hand, and it costs one step in the workflow.

• URL: required, the URL to validate.