Automate Gmail + HubSpot
The inbox most operations still start in. 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.
Support First Responder already works across Gmail and HubSpot — free, and it runs on your machine.
Automations teams run
These are not field mappings. An agent reads the Gmail side, works out what it means, and only then decides what — if anything — should happen in HubSpot.
When a new email arrives in Gmail…
…an agent can create and enrich contacts in HubSpot — after reading the context and deciding it should.
When a label is applied in Gmail…
…an agent can update deals and notes in HubSpot — after reading the context and deciding it should.
When a thread goes unanswered in Gmail…
…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 send or draft a reply in Gmail — with the reasoning recorded in the run’s receipt.
When a stage changes in HubSpot…
…an agent can apply labels and archive in Gmail — with the reasoning recorded in the run’s receipt.
When a form submits in HubSpot…
…an agent can extract attachments and fields in Gmail — with the reasoning recorded in the run’s receipt.
Gmail to HubSpot, setup template
Start with the gmail-api node and a custom-api call to api.hubapi.com. Configure the Gmail 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": "6b4b95eb-eb6c-4db5-a010-403a3613eeaa",
"name": "Gmail → HubSpot",
"nodes": [
{
"id": "dc05bce7-511f-4d5a-a631-44d1636935e0",
"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": "4702de62-3218-47d2-a9b0-e8b8a6069fe0",
"text": "Read Gmail",
"x": 512,
"y": 336,
"isEditing": false,
"type": "gmail-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "Search and Read Emails",
"searchQuery": "CONFIGURE_SEARCHQUERY",
"maxResults": 1
},
"description": "Setup template for Gmail API. A powerful tool to send, reply, read, organize, and manage attachments in Gmail. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "a2321515-9876-4634-acc4-6b89c82a9408",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Gmail 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": "13558351-c9f5-40b5-ae9a-e0b4ca5c23ba",
"text": "Call HubSpot",
"x": 512,
"y": 720,
"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": "f85cc8f2-f04d-4a7f-a79f-41fd3366b59a",
"start": {
"id": "dc05bce7-511f-4d5a-a631-44d1636935e0",
"type": "output"
},
"end": {
"id": "4702de62-3218-47d2-a9b0-e8b8a6069fe0",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "84f3a02a-4c76-42d4-a245-3e3e3ee42628",
"start": {
"id": "4702de62-3218-47d2-a9b0-e8b8a6069fe0",
"type": "output"
},
"end": {
"id": "a2321515-9876-4634-acc4-6b89c82a9408",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "d1a4d447-c2f1-4283-a8c9-f382cdf6c10a",
"start": {
"id": "a2321515-9876-4634-acc4-6b89c82a9408",
"type": "output"
},
"end": {
"id": "13558351-c9f5-40b5-ae9a-e0b4ca5c23ba",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Gmail API
A powerful tool to send, reply, read, organize, and manage attachments in Gmail.
- operation — The Gmail operation to perform. Current example:
Search and Read Emails. - searchQuery — Optional. Gmail search query (e.g., 'from:user is:unread'). If blank, fetches latest emails. Current example:
CONFIGURE_SEARCHQUERY. - maxResults — Maximum number of emails to return. Current example:
1.
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 Support First Responder
Support First Responder already uses both Gmail 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
What building this looks like
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise HubSpot (one OAuth sign-in) and Gmail (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; gmail-api does the reading and custom-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Gmail and HubSpot — common questions
Can I connect Gmail to HubSpot without writing code?
No code is required. Add both connections in the vault (Gmail uses one OAuth sign-in, HubSpot 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 Gmail to HubSpot automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Gmail item in full and decides — whether it matters, how to summarise it, and what belongs in HubSpot. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Gmail and HubSpot 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: Gmail, HubSpot, and your chosen model provider — which can be a local one.
What does a Gmail and HubSpot run leave behind?
A receipt: what was read in Gmail, 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.
