Bedrijfsdata icon

Bedrijfsdata

Get data from the Bedrijfsdata API.

Overview

This node integrates with the Bedrijfsdata API to retrieve various types of business-related data. Specifically, for the Other Data resource and the Get EU Tenders operation, it queries the European Tender database to fetch tender information based on a user-provided search query.

This functionality is useful for businesses or professionals who want to monitor public procurement opportunities across Europe, analyze market competition, or gather intelligence on upcoming projects. For example, a company looking to bid on government contracts can use this node to find relevant tenders by keywords or specific criteria.

Properties

Name Meaning
Search Query (Required) Enter a search query string to retrieve matching EU tenders from the database.

The property corresponds to a text input where users specify their search terms. The node uses this query to filter tenders in the European Tender database.

Output

  • The node outputs JSON data containing the results returned by the Bedrijfsdata API's /tender endpoint.
  • The structure typically includes an array of tender records matching the search query, each with details such as tender title, description, dates, and other metadata provided by the API.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Bedrijfsdata API via an API key credential configured in n8n.
  • The node sends HTTP GET requests to https://api.bedrijfsdata.nl/v1.2/tender with the search query as a URL parameter.
  • Proper network access and valid API credentials are necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing an empty or malformed search query may result in no data or API errors.
    • Network connectivity problems can prevent the node from reaching the API endpoint.
  • Error messages:

    • Errors related to API request failures will be thrown as node operation errors with descriptive messages.
    • If the API returns unexpected responses, the node may throw errors indicating failure to fetch or parse tender data.
  • Resolutions:

    • Ensure the API key credential is correctly set up and has sufficient permissions.
    • Verify that the search query is properly formatted and not empty.
    • Check internet connectivity and firewall settings allowing outbound HTTPS requests to the API domain.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion