Automate Airtable + HubSpot
Structured records with an API worth automating. The CRM your pipeline reporting depends on. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Lead Researcher already works across Airtable and HubSpot — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Airtable into HubSpot.
When a record is created in Airtable…
…an agent can create and enrich contacts in HubSpot — after reading the context and deciding it should.
When a field changes in Airtable…
…an agent can update deals and notes in HubSpot — after reading the context and deciding it should.
When a view gains a row in Airtable…
…an agent can log activity in HubSpot — after reading the context and deciding it should.
When a contact or deal is created in HubSpot…
…an agent can create and update records in Airtable — with the reasoning recorded in the run’s receipt.
When a stage changes in HubSpot…
…an agent can query views for reporting in Airtable — with the reasoning recorded in the run’s receipt.
When a form submits in HubSpot…
…an agent can link records across tables in Airtable — with the reasoning recorded in the run’s receipt.
The Airtable and HubSpot hand-off, setup template
Start with a custom-api call to api.airtable.com and a custom-api call to api.hubapi.com. Configure the Airtable source payload, the agent input, and the HubSpot operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "3be1f899-ca7c-4265-ae46-f996c9bb8d66",
"name": "Airtable → HubSpot",
"nodes": [
{
"id": "1d7f99b3-0e20-4840-ab1f-1dd38844d4e4",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "83e00739-d770-43e1-a039-324cea23dcde",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Airtable item. Decide whether it warrants action in HubSpot, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "4c84b71d-d8e4-4a10-a8ee-d373b0ca2c38",
"text": "Call HubSpot",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.hubapi.com/crm/v3/objects/contacts",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "ec7092c1-46a6-4429-aba3-01f63d9d7712",
"start": {
"id": "1d7f99b3-0e20-4840-ab1f-1dd38844d4e4",
"type": "output"
},
"end": {
"id": "83e00739-d770-43e1-a039-324cea23dcde",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "7b679c4f-a5e1-4008-a9a9-3ce58befe068",
"start": {
"id": "83e00739-d770-43e1-a039-324cea23dcde",
"type": "output"
},
"end": {
"id": "4c84b71d-d8e4-4a10-a8ee-d373b0ca2c38",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://api.hubapi.com/crm/v3/objects/contacts. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install Lead Researcher
Lead Researcher already uses both Airtable and HubSpot, so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
Runs on your own machine · See what it does
Wiring Airtable to HubSpot
- Download AGNT Community Core — free and local-first.
- Connect Airtable with an API key pasted into the vault and HubSpot with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and a custom-api node onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Airtable and what was written to HubSpot.
Airtable and HubSpot — common questions
Can I connect Airtable to HubSpot without writing code?
Yes. Airtable connects with an API key pasted into the vault and HubSpot with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a record is created, create and enrich contacts” — and the agent handles the rest.
How is this different from a field-mapping Airtable to HubSpot automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles pipeline trackers that stay current the way a colleague would — reading the Airtable context, judging it, then writing to HubSpot with the reasoning recorded.
Does my Airtable and HubSpot data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Airtable or HubSpot tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Airtable and HubSpot run leave behind?
A receipt: what was read in Airtable, which tools ran with which arguments, what the agent concluded, and what it wrote to HubSpot. Anything consequential can sit behind an approval gate so a person signs off before it happens.
