Automate Gmail + Linear
The inbox most operations still start in. 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.
Inbox Triage is a ready-made agent built around Gmail; point its last step at Linear to finish this hand-off.
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 Linear.
When a new email arrives in Gmail…
…an agent can create issues with full context in Linear — after reading the context and deciding it should.
When a label is applied in Gmail…
…an agent can update status and assignees in Linear — after reading the context and deciding it should.
When a thread goes unanswered in Gmail…
…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 send or draft a reply in Gmail — with the reasoning recorded in the run’s receipt.
When a status changes in Linear…
…an agent can apply labels and archive in Gmail — with the reasoning recorded in the run’s receipt.
When a cycle ends in Linear…
…an agent can extract attachments and fields in Gmail — with the reasoning recorded in the run’s receipt.
Copy this Gmail → Linear workflow
Start with the gmail-api node and a custom-api call to api.linear.app. Configure the Gmail source payload, the agent input, and the Linear 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": "9232a112-68bf-4a39-adf5-405b4b562dde",
"name": "Gmail → Linear",
"nodes": [
{
"id": "83444c7c-65e0-4582-a5c0-a0b22f644720",
"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": "fd77b133-5267-4caf-ae4e-e662ab3259d6",
"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": "653db3af-1da9-4696-a519-17273d65143c",
"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 Linear, 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": "dd374967-749e-4c4f-a0ec-307465e90576",
"text": "Call Linear",
"x": 512,
"y": 720,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.linear.app/graphql",
"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": "7a59a052-982e-4831-a542-bbc78f5f8b62",
"start": {
"id": "83444c7c-65e0-4582-a5c0-a0b22f644720",
"type": "output"
},
"end": {
"id": "fd77b133-5267-4caf-ae4e-e662ab3259d6",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "09d4a6e4-bd9e-4142-a134-62a611f68708",
"start": {
"id": "fd77b133-5267-4caf-ae4e-e662ab3259d6",
"type": "output"
},
"end": {
"id": "653db3af-1da9-4696-a519-17273d65143c",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "58a986f7-b504-409f-a97a-15e20ed14b0a",
"start": {
"id": "653db3af-1da9-4696-a519-17273d65143c",
"type": "output"
},
"end": {
"id": "dd374967-749e-4c4f-a0ec-307465e90576",
"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.linear.app/graphql. - 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 Inbox Triage
Inbox Triage is a working agent built around Gmail. 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
What building this looks like
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Gmail takes one OAuth sign-in, Linear takes an API key pasted into the vault.
- Configure the 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.
Gmail and Linear — common questions
Can I connect Gmail to Linear without writing code?
Yes. Gmail 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 new email arrives, create issues with full context” — and the agent handles the rest.
How is this different from a field-mapping Gmail to Linear 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 Linear. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Gmail 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: Gmail, Linear, and your chosen model provider — which can be a local one.
What does a Gmail and Linear 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 Linear. Anything consequential can sit behind an approval gate so a person signs off before it happens.
