Automate HubSpot + Slack
The CRM your pipeline reporting depends on. Team chat where operations actually surface. 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 HubSpot and Slack — 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 HubSpot into Slack.
When a contact or deal is created in HubSpot…
…an agent can post a rich channel message in Slack — after reading the context and deciding it should.
When a stage changes in HubSpot…
…an agent can DM a teammate in Slack — after reading the context and deciding it should.
When a form submits in HubSpot…
…an agent can open a thread with findings in Slack — after reading the context and deciding it should.
When a message hits a channel in Slack…
…an agent can create and enrich contacts in HubSpot — with the reasoning recorded in the run’s receipt.
When a keyword or mention fires in Slack…
…an agent can update deals and notes in HubSpot — with the reasoning recorded in the run’s receipt.
When a reaction is added in Slack…
…an agent can log activity in HubSpot — with the reasoning recorded in the run’s receipt.
HubSpot to Slack, in three nodes
The two ends are a custom-api call to api.hubapi.com and the slack-api node. What makes this different from a zap is the middle node — it forms a view about the HubSpot item before anything reaches Slack.
{
"id": "398604b7-717b-4327-a27d-356aaae2c41a",
"name": "HubSpot → Slack",
"nodes": [
{
"id": "9fb50c46-c6bf-414f-a636-8da36bda14ce",
"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": "0c1b8abe-bb36-4599-a73c-4d31f83d227e",
"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 Slack, and explain why."
},
"description": "Decides whether this HubSpot item warrants anything in Slack.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "bdfd2d28-07a7-4032-a7a5-d3d8f9d7ee0c",
"text": "Act in Slack",
"x": 512,
"y": 528,
"isEditing": false,
"type": "slack-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "SEND_MESSAGE"
},
"description": "Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "73247724-0be9-4f41-a8e5-7427a6047a22",
"start": {
"id": "9fb50c46-c6bf-414f-a636-8da36bda14ce",
"type": "output"
},
"end": {
"id": "0c1b8abe-bb36-4599-a73c-4d31f83d227e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "07bc4dfb-759f-4872-a7c4-b70329690484",
"start": {
"id": "0c1b8abe-bb36-4599-a73c-4d31f83d227e",
"type": "output"
},
"end": {
"id": "bdfd2d28-07a7-4032-a7a5-d3d8f9d7ee0c",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Lead Researcher
Lead Researcher already uses both HubSpot and Slack, 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
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect HubSpot with one OAuth sign-in and Slack with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and slack-api 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 HubSpot and what was written to Slack.
HubSpot and Slack — common questions
Can I connect HubSpot to Slack without writing code?
No code is required. Add both connections in the vault (HubSpot uses one OAuth sign-in, Slack uses one OAuth sign-in), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping HubSpot to Slack automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Slack, 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 Slack data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to HubSpot, Slack and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a HubSpot and Slack 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 Slack. Anything consequential can sit behind an approval gate so a person signs off before it happens.
