Automate HubSpot + Linear
The CRM your pipeline reporting depends on. Fast issue tracking that deserves fast automation. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Lead Researcher is a ready-made agent built around HubSpot; point its last step at Linear to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Linear is a decision about the HubSpot event rather than a transcription of it.
When a contact or deal is created in HubSpot…
…an agent can create issues with full context in Linear — after reading the context and deciding it should.
When a stage changes in HubSpot…
…an agent can update status and assignees in Linear — after reading the context and deciding it should.
When a form submits in HubSpot…
…an agent can write cycle summaries in Linear — after reading the context and deciding it should.
When an issue is created in Linear…
…an agent can create and enrich contacts in HubSpot — with the reasoning recorded in the run’s receipt.
When a status changes in Linear…
…an agent can update deals and notes in HubSpot — with the reasoning recorded in the run’s receipt.
When a cycle ends in Linear…
…an agent can log activity in HubSpot — with the reasoning recorded in the run’s receipt.
HubSpot to Linear, in three nodes
Concretely: a custom-api call to api.hubapi.com on one side, a custom-api call to api.linear.app on the other, and an agent in between that can decline. Deciding not to write into Linear is a recorded outcome, not a silent one.
{
"id": "72af1208-c4a4-4e50-a0b1-a8d2fc160a00",
"name": "HubSpot → Linear",
"nodes": [
{
"id": "aa4453a5-b897-42d3-afdf-ea5a4f0c1f22",
"text": "Poll HubSpot",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"interval": "15",
"unit": "minutes"
},
"description": "Checks HubSpot on a schedule.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3bcaaa8a-34b7-432e-ab8a-0e223c337be4",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the HubSpot item. Decide whether it warrants action in Linear, and explain why."
},
"description": "Decides whether this HubSpot item warrants anything in Linear.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "c795662e-be9c-49b9-aecc-fffb810b0682",
"text": "Call Linear",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.linear.app/graphql",
"method": "POST"
},
"description": "Writes into Linear over its API.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "47dcc790-495e-448c-af14-27d4a51aaea0",
"start": {
"id": "aa4453a5-b897-42d3-afdf-ea5a4f0c1f22",
"type": "output"
},
"end": {
"id": "3bcaaa8a-34b7-432e-ab8a-0e223c337be4",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b748fe2b-1067-4c51-a6d3-255e6150cd62",
"start": {
"id": "3bcaaa8a-34b7-432e-ab8a-0e223c337be4",
"type": "output"
},
"end": {
"id": "c795662e-be9c-49b9-aecc-fffb810b0682",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Lead Researcher
Lead Researcher is a working agent built around HubSpot. Install it, point its last step at Linear, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring HubSpot to Linear
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — HubSpot takes one OAuth sign-in, Linear takes an API key pasted into the vault.
- Build the three nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Linear.
HubSpot and Linear — common questions
Can I connect HubSpot to Linear without writing code?
Yes. HubSpot connects with one OAuth sign-in and Linear with an API key pasted into the vault, both from the local credential vault. You then describe the job in plain language — “when a contact or deal is created, create issues with full context” — and the agent handles the rest.
How is this different from a field-mapping HubSpot to Linear automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Linear, the agent can weigh what arrived from HubSpot, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my HubSpot and Linear data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: HubSpot, Linear, and your chosen model provider — which can be a local one.
What does a HubSpot and Linear run leave behind?
A receipt: what was read in HubSpot, which tools ran with which arguments, what the agent concluded, and what it wrote to Linear. Anything consequential can sit behind an approval gate so a person signs off before it happens.
