Back to Catalog

Enrich HubSpot companies with Bedrijfsdata.nl

OlivierOlivier
130 views
2/3/2026
Official Page

This template enriches HubSpot company records using real-time data from the Bedrijfsdata.nl API. It listens for changes to company properties (e.g., domain) and updates records with verified information such as KvK, LinkedIn, phone, and company size.


โœจ Features

  • Automatically enrich HubSpot company profiles with verified Dutch business data
  • Smart fallback: match by Bedrijfsdata ID or dynamic fuzzy matching existing data
  • Customize which HubSpot event triggers the workflow (company.propertyChange, create, etc.)
  • Realtime integration with Bedrijfsdata.nl via their official API node
  • Secure, modular, and extendable structure (error handling included)

๐Ÿข Example Data from Bedrijfsdata.nl

Bedrijfsdata.nl offers over 100 attributes per company. Example fields:

  • name, address, postcode, city, province
  • phone, email, website, linkedin_link
  • industry_section, employees, revenue, sbi, vat
  • bag_bouwjaar, bag_oppervlakte, bag_energielabel
  • SEO data (keywords, backlinks), usage of software, structured descriptions
  • Review ratings, opening hours, geo-location, etc.

Example:
Bedrijfsdata.nl B.V.

  • Phone: 020-7895050
  • Mail: klantenservice@bedrijfsdata.nl
  • Employees: 2-10
  • SBI: 6201
  • LinkedIn: linkedin.com/company/bedrijfsdata-nl
  • Description: Bedrijfsdata.nl B.V. is a Dutch company that provides comprehensive data on over 3.1 million businesses in the Netherlands. They offer datasets categorized by industry, region, company [...]
  • More fields: see developers.bedrijfsdata.nl

โš™ Requirements

  • n8n instance or cloud workspace
  • Install the Bedrijfsdata.nl n8n Verified Community Node
  • HubSpot private app (OAuth2) with a webhook
  • Bedrijfsdata.nl developer account (14-day free trial, 500 credits)

๐Ÿ”ง Setup Instructions

  1. Create HubSpot Private App

    • Enable scopes for companies
    • Add a webhook to listen to e.g. company.propertyChange on domain
    • More info: HubSpot Private Apps
  2. Configure n8n Workflow

    • Import this template
    • Set your Bedrijfsdata.nl API credentials
    • Set up HubSpot OAuth2 credentials
  3. Customize Fields (Optional)

    • Modify the Update a company node to match your internal CRM fields
    • Add logging, Slack notifications, or conditional branches if needed

๐Ÿ” Security Notes

  • Workflow checks portalId, objectId, and event type
  • Test-mode detection using a known company ID
  • Errors are routed via dedicated error branches

๐Ÿงช Testing

  1. Create or update a company in HubSpot with a known domain
  2. Trigger the webhook from HubSpot
  3. Check n8nโ€™s execution history
  4. Verify enrichment in HubSpot

๐Ÿ–ผ Screenshots

Before enrichment
Before

After enrichment
After


๐Ÿ“Œ About Bedrijfsdata.nl

Bedrijfsdata.nl operates the most comprehensive company database in the Netherlands. With real-time data on 3.7M+ businesses and AI-ready APIs, we help Dutch SMEs enrich their CRM, workflows, and marketing automation. Built on 25+ years of experience in data collection and enrichment, our technology brings corporate-grade data quality to every organisation.

Website: https://www.bedrijfsdata.nl
Developers: developers.bedrijfsdata.nl


๐Ÿ“ž Support

  • Email: klantenservice@bedrijfsdata.nl
  • Phone: +31 20 789 50 50
  • Support hours: Mondayโ€“Friday, 09:00โ€“17:00 CET

n8n Workflow: Basic Webhook Trigger with Conditional Logic

This n8n workflow demonstrates a fundamental setup for receiving data via a webhook, applying conditional logic, and then performing a subsequent action (or doing nothing) based on that logic. It's a versatile template for starting any workflow that needs to react to external events and make decisions.

What it does

This workflow simplifies the process of:

  1. Receiving External Data: It listens for incoming HTTP requests (webhooks).
  2. Applying Conditional Logic: It evaluates the received data against a defined condition.
  3. Branching Workflow Execution: Based on the condition's outcome, it directs the workflow to either a "true" path (where an action like updating HubSpot would typically occur) or a "false" path (where no action is currently defined).

Key Steps

  1. Webhook Trigger: The workflow starts by exposing a unique URL that can receive HTTP POST requests. Any data sent to this URL will initiate the workflow.
  2. Conditional Check (If Node): The data received from the webhook is then passed to an "If" node. This node is configured to evaluate a specific condition on the incoming data.
  3. HubSpot Action (True Path): If the condition in the "If" node evaluates to true, the workflow proceeds to a "HubSpot" node. Note: The specific operation for the HubSpot node is not defined in the provided JSON, but this is where you would configure actions like creating or updating a company, contact, or deal in HubSpot.
  4. No Operation (False Path): If the condition in the "If" node evaluates to false, the workflow proceeds to a "No Operation, do nothing" node. This path essentially ends the workflow for items that do not meet the specified condition.
  5. Code Node (Unconnected): There is an unconnected "Code" node present in the workflow. This node is typically used for custom JavaScript logic, data transformation, or more complex conditional checks that cannot be handled by standard nodes. It is currently inactive.
  6. Sticky Note (Unconnected): A "Sticky Note" is included, likely for documentation or reminders within the workflow canvas. It does not affect workflow execution.

Prerequisites/Requirements

  • n8n Instance: An active n8n instance (cloud or self-hosted) to import and run the workflow.
  • Webhook Source: An external application or service capable of sending HTTP POST requests to the n8n webhook URL.
  • HubSpot Account: If you intend to use the HubSpot integration, you will need a HubSpot account and appropriate API credentials configured in n8n.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON content.
    • In your n8n instance, click on "Workflows" in the left sidebar.
    • Click "New" or "Add Workflow".
    • Click the three-dot menu (...) in the top right and select "Import from JSON".
    • Paste the JSON content and click "Import".
  2. Configure the Webhook:
    • Open the "Webhook" node.
    • The "Webhook URL" will be automatically generated. Copy this URL.
    • Configure your external application or service to send POST requests to this URL.
  3. Configure the If Node:
    • Open the "If" node.
    • Define the condition(s) that the incoming webhook data should meet. For example, you might check if a specific field in the JSON payload equals a certain value.
  4. Configure HubSpot (if applicable):
    • Open the "HubSpot" node.
    • Select or create a HubSpot credential.
    • Configure the desired operation (e.g., "Create/Update Company", "Create Contact") and map the data from the incoming webhook to the relevant HubSpot fields.
  5. Activate the Workflow:
    • Once configured, toggle the workflow to "Active" in the top right corner of the n8n editor.

Now, whenever your external service sends data to the webhook URL, the workflow will execute, evaluate the condition, and perform the HubSpot action if the condition is met.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorโ€™s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger โ€” Manually start the workflow or schedule it to run periodically. Input Setup โ€” Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) โ€” Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring โ€” Clean and convert GPT output into JSON format. Data Storage (Google Sheets) โ€” Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the โ€œSet Input Fieldsโ€ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors โ†’ Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection โ†’ Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report โ†’ Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization โ†’ Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs โ†’ Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itโ€™s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chatโ€”turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. ๐Ÿ“‹ What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing ๐Ÿ”ง Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation ๐Ÿ”‘ Required Credentials OpenAI API Setup Go to platform.openai.com โ†’ API keys (sidebar) Click "Create new secret key" โ†’ Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai โ†’ Dashboard โ†’ API Keys Generate a new API key โ†’ Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) โš™๏ธ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowโ€”chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" ๐ŸŽฏ Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration โš ๏ธ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive โžœ Download PDF โžœ OCR text โžœ AI normalize to JSON โžœ Upsert Buyer (Account) โžœ Create Opportunity โžœ Map Products โžœ Create OLI via Composite API โžœ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content โ†’ the parsed JSON (ensure itโ€™s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id โžœ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total โžœ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger โ†’ Download File From Google Download File From Google โ†’ Extract from File โ†’ Update File to One Drive Extract from File โ†’ Message a model Message a model โ†’ Create or update an account Create or update an account โ†’ Create an opportunity Create an opportunity โ†’ Build SOQL Build SOQL โ†’ Query PricebookEntries Query PricebookEntries โ†’ Code in JavaScript Code in JavaScript โ†’ Create Opportunity Line Items --- Quick setup checklist ๐Ÿ” Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. ๐Ÿ“‚ IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) ๐Ÿง  AI Prompt: Use the strict system prompt; jsonOutput = true. ๐Ÿงพ Field mappings: Buyer tax id/name โ†’ Account upsert fields Invoice code/date/amount โ†’ Opportunity fields Product name must equal your Product2.ProductCode in SF. โœ… Test: Drop a sample PDF โ†’ verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep โ€œReturn only a JSON arrayโ€ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donโ€™t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgโ€™s domain or use the Salesforce nodeโ€™s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942