Built In hiring companies to HubSpot with n8n

Tech companies from the Built In directory arrive in HubSpot as company records with their name, Built In profile link as the website, headquarters city, employee count and the number of open jobs in the description. Each company is created once, so a daily run adds only companies new to your list.

You need a HubSpot private app token with permission to write companies, stored in an n8n Header Auth credential as Bearer plus the token. The starter input browses the directory and asks for 1 company; raise maxItems and set a location or hiring filter in the request body before the first scheduled run.

Run on Apify

Built-in nodes only Imports on n8n Cloud and self-hosted n8n 1.80 or later, no community nodes. 11 of 11 checks pass; validated, not executed.

Source: Built In
Actor: BuiltIn Tech Company Directory & Hiring Signal Scraper
Destination: HubSpot
Store price: $0.99 per 1,000 results (pay per event)
Cost on the Free plan: about $0.10 a run (start $0.10 + up to 1 result), about $3.03 a month daily, plus platform usage
Data checked: 2026-11-12

Method

Get an Apify token

Sign in to Apify and copy a personal API token from Console: Settings, API and integrations. The workflow keeps it in an n8n credential, never in the file.

Import the workflow

In n8n choose Workflows, Import from file, or paste the JSON onto an empty canvas.

Run by hand
Every day
Run Apify Actor
Only records not sent before
Send to HubSpot

n8n workflowbuilt-in-hiring-leads-to-hubspot.n8n.json

Actor on Apify

Show the file (173 lines)

{
  "name": "Built In hiring companies to HubSpot",
  "nodes": [
    {
      "id": "a49124aa-7ef2-49b2-a12f-235faf38b43b",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "2319016a-705a-4c2c-ad09-771d45917163",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "060a6c4e-345f-4bd9-a7c0-cd1498258583",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/nimbryxo-studio~builtin-tech-company-directory-and-hiring-signal/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"mode\": \"browse\",\n  \"hiringOnly\": false,\n  \"remoteJobsOnly\": false,\n  \"includeDetails\": false,\n  \"includeProfile\": false,\n  \"includeJobCards\": false,\n  \"includeBenefits\": false,\n  \"maxItems\": 1\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: nimbryxo-studio/builtin-tech-company-directory-and-hiring-signal. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "a10daa3a-d831-4b0a-a0e7-c4c715846043",
      "name": "Only records not sent before",
      "type": "n8n-nodes-base.removeDuplicates",
      "typeVersion": 2,
      "position": [
        500,
        100
      ],
      "parameters": {
        "operation": "removeItemsSeenInPreviousExecutions",
        "logic": "removeItemsWithAlreadySeenKeyValues",
        "dedupeValue": "={{ $json.builtInUrl }}",
        "options": {
          "scope": "node",
          "historySize": 10000
        }
      },
      "notes": "Remembers each builtInUrl it has passed on (up to 10,000) across runs, so a record is sent once. Needs n8n 1.64 or later."
    },
    {
      "id": "f86bef72-5bc8-4a34-ae79-6dad50cf51bb",
      "name": "Send to HubSpot",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        740,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.hubapi.com/crm/v3/objects/companies",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "={{ JSON.stringify({ properties: Object.fromEntries(Object.entries({ name: $json.name || $json.title || $json.companyName, website: $json.website || $json.url || $json.builtInUrl, city: $json.city || $json.headquarters, numberofemployees: $json.employeeCount, description: $json.openJobsCount !== undefined ? 'Open jobs: ' + $json.openJobsCount : $json.description }).filter(([, v]) => v !== undefined && v !== null && v !== '')) }) }}",
        "options": {}
      },
      "notes": "Create a Header Auth credential: name Authorization, value Bearer + your HubSpot private app token (crm.objects.companies.write). Each record becomes a company.",
      "onError": "continueRegularOutput"
    },
    {
      "id": "52eb7132-7603-4d10-a3da-4cf5406595c7",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## BuiltIn Tech Company Directory & Hiring Signal Scraper\n\nSource: [nimbryxo-studio/builtin-tech-company-directory-and-hiring-signal](https://apify.com/nimbryxo-studio/builtin-tech-company-directory-and-hiring-signal) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Open **Send to Webhook** and replace the URL with yours.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Run Apify Actor": {
      "main": [
        [
          {
            "node": "Only records not sent before",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Only records not sent before": {
      "main": [
        [
          {
            "node": "Send to HubSpot",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Validated, not executed: 11 of 11 checks pass

It has a nodes array and a connections object
Every node has a name, type, typeVersion, position and parameters
Node names are unique
Every node type is a known n8n core node (or the Apify node)
Every node uses a typeVersion that n8n ships
Every connection points at an existing node
At least one trigger starts the workflow
Every working node is reachable from a trigger
Apify calls use POST and a credential for the token
Actor input matches the Actor's published input schema
No token or credential value is embedded

Add the Apify credential

Open Run Apify Actor. Under Credential, create a Header Auth credential with the name Authorization and the value Bearer, a space and your token.
Set the input

The request body holds the Actor input. It starts from the Actor's Store prefill; change mode, hiringOnly, remoteJobsOnly to match your search.
```
{
  "mode": "browse",
  "hiringOnly": false,
  "remoteJobsOnly": false,
  "includeDetails": false,
  "includeProfile": false,
  "includeJobCards": false,
  "includeBenefits": false,
  "maxItems": 1
}
```
Every input field is documented on the BuiltIn Tech Company Directory & Hiring Signal Scraper page.
Only new records go through

The Only records not sent before node (n8n's Remove Duplicates, set to remove items processed in previous executions) remembers each builtInUrl it has passed on, so a record reaches HubSpot once even when the next run returns it again. It needs n8n 1.64 or later; clear its history from the node to resend everything.
Connect HubSpot

Open Send to HubSpot and create a Header Auth credential: name Authorization, value Bearer plus a HubSpot private app token with contact write access.
Run once, then turn it on

Click Execute workflow and check the first records in HubSpot. When they look right, activate the workflow so the daily trigger runs it at 08:00 in your instance's timezone.

Where it breaks

Built In lists company profiles, not people, so no contacts, emails or phone numbers are created.
If HubSpot already has a matching company and rejects the record, that record is skipped and the run continues.
Open job counts change daily; the description holds the number at the time the company was created.
The workflow uses Apify's synchronous endpoint, which waits up to 300 seconds. Bigger runs answer HTTP 408: lower the limit or switch to an asynchronous run.
Each run is billed to your Apify account at the Store price ($0.99 per 1,000 results (pay per event)).

Bigger runs: the long-run workflow starts the run, waits for it and reads the dataset, so it never hits the 300-second limit.

If the workflow fails

Why does the workflow or script stop with HTTP 408?

The synchronous endpoint waits at most 300 seconds. After that it answers 408 while the run keeps going in Apify. Lower the result limit, or start the run asynchronously, wait for it to finish and then read its dataset.

Source: Apify API: run Actor synchronously and get dataset items

What do 400, 401, 402 and 403 from the Apify API mean?

Read error.type in the response body. 400 is invalid Actor input. 401 (user-or-token-not-found) means a token reached Apify but it is wrong or revoked. 402 with x402-payment-required means no token reached Apify at all: the n8n credential or the Authorization: Bearer header is missing, and Apify is offering its pay-per-run x402 route for agents instead; any other 402 is an exhausted usage limit on the account that pays for the run. 403 is a token without permission for that Actor or storage.

Source: Apify API: authentication; Apify documentation: agentic payments with x402; Apify API: run Actor synchronously and get dataset items

n8n says Install this node to use it after import. Why?

The workflow names a node or node version your instance does not have, usually a community node. The workflows here use only built-in nodes at versions n8n has shipped since 1.80, so they import on n8n Cloud and older self-hosted instances without community nodes.

Source: n8n issue: unrecognized node type after import

Why does the HTTP Request node time out before Apify answers?

Set the node's Timeout option to at least 300000 ms so n8n waits as long as Apify's synchronous endpoint. The workflows here already set 310000. A failure at exactly 30 seconds points to a proxy in front of n8n.

Source: n8n HTTP Request node documentation

Every fix in one place

Same data in an agent

Want Claude, Cursor or ChatGPT to call the Actor directly instead of on a schedule? The BuiltIn Tech Company Directory & Hiring Signal Scraper page has MCP configs for eight clients and a SKILL.md. The Built In MCP server bundles every Built In Actor in one URL.

Questions

Which HubSpot permission does the token need?

Write access to CRM companies. Create a private app in HubSpot, grant it company write access and paste its token into the credential as Bearer plus the token.

Can I keep only companies that are hiring?

Yes. Switch hiringOnly on in the request body and only companies with open roles come back.

More recipes

Google Maps leads to HubSpot
Send a Google Maps business search into HubSpot as contacts, one contact per place with its name, phone…
Google MapsHubSpot

Built In hiring companies to HubSpot with n8n

Method

Get an Apify token

Import the workflow

n8n workflowbuilt-in-hiring-leads-to-hubspot.n8n.json

Add the Apify credential

Set the input

Only new records go through

Connect HubSpot

Run once, then turn it on

Where it breaks

If the workflow fails

Same data in an agent

Questions

More recipes

Google Maps leads to HubSpot