Automate Google Drive + Linear
Where the documents live — and pile up. 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.
Document Extractor is a ready-made agent built around Google Drive; point its last step at Linear to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Google Drive side, works out what it means, and only then decides what — if anything — should happen in Linear.
When a file lands in a folder in Google Drive…
…an agent can create issues with full context in Linear — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can update status and assignees in Linear — after reading the context and deciding it should.
When a file is shared in Google Drive…
…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 read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a status changes in Linear…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a cycle ends in Linear…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Linear, setup template
Start with the google-drive-api node and a custom-api call to api.linear.app. Configure the Google Drive 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": "8787bddd-7849-46a7-a6c0-fa9cff422fc6",
"name": "Google Drive → Linear",
"nodes": [
{
"id": "3a78f0fe-7c5c-4395-a9eb-6905c929b686",
"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": "dec24511-b88f-48f2-a04c-cdd710ad7c1c",
"text": "Read Google Drive",
"x": 512,
"y": 336,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_FILES",
"folderId": "CONFIGURE_FOLDERID"
},
"description": "Setup template for Google Drive API. Interact with Google Drive to perform various operations on files and folders. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "103c4e81-0573-4aab-a50d-7bb2f8a669b6",
"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 Google Drive 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": "a3ac684f-64b5-4594-af28-08c98a135334",
"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": "a5827b11-eca4-4776-a124-1377682069f4",
"start": {
"id": "3a78f0fe-7c5c-4395-a9eb-6905c929b686",
"type": "output"
},
"end": {
"id": "dec24511-b88f-48f2-a04c-cdd710ad7c1c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "19ccebc5-5ba6-45ad-a83b-bcf2e6dd9a52",
"start": {
"id": "dec24511-b88f-48f2-a04c-cdd710ad7c1c",
"type": "output"
},
"end": {
"id": "103c4e81-0573-4aab-a50d-7bb2f8a669b6",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "822da979-4851-4d2c-a82b-89dd6015d70c",
"start": {
"id": "103c4e81-0573-4aab-a50d-7bb2f8a669b6",
"type": "output"
},
"end": {
"id": "a3ac684f-64b5-4594-af28-08c98a135334",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Drive API
Interact with Google Drive to perform various operations on files and folders.
- action — The action to perform on Google Drive Current example:
LIST_FILES. - folderId — The ID of the folder (for LIST_FILES, UPLOAD_FILE, CREATE_FOLDER) Current example:
CONFIGURE_FOLDERID.
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 Document Extractor
Document Extractor is a working agent built around Google Drive. 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
- Download AGNT Community Core — free and local-first.
- Connect Google Drive with one OAuth sign-in and Linear with an API key pasted into the vault; both land in the local vault.
- Start from a marketplace workflow, or drop google-drive-api 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 Google Drive and what was written to Linear.
Google Drive and Linear — common questions
Can I connect Google Drive to Linear without writing code?
No code is required. Add both connections in the vault (Google Drive uses one OAuth sign-in, Linear uses an API key pasted into the vault), 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 Google Drive 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 Google Drive, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Drive 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: Google Drive, Linear, and your chosen model provider — which can be a local one.
What does a Google Drive and Linear run leave behind?
You get an auditable trail rather than a success flag. It shows the Google Drive context the agent worked from, the judgment it made about support escalations become tracked issues, and the exact change applied in Linear, with approvals attached where you required them.
