Automate Google Drive + Jira
Where the documents live — and pile up. The ticket system of record for engineering work. 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 Jira to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Jira is a decision about the Google Drive event rather than a transcription of it.
When a file lands in a folder in Google Drive…
…an agent can create and update issues in Jira — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can transition tickets with comments in Jira — after reading the context and deciding it should.
When a file is shared in Google Drive…
…an agent can summarise sprint state in Jira — after reading the context and deciding it should.
When an issue is created or transitions in Jira…
…an agent can read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a sprint starts in Jira…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a priority changes in Jira…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Jira, setup template
Start with the google-drive-api node and a custom-api call to {yoursite}.atlassian.net. Configure the Google Drive source payload, the agent input, and the Jira 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": "e7e981dd-0f40-4ad1-a28c-2038a8c9dfde",
"name": "Google Drive → Jira",
"nodes": [
{
"id": "3fcbda46-7b75-495a-a547-1a28bd118bd4",
"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": "afc45d99-04f6-4789-a27b-a2e23b697096",
"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": "1393b62a-9a32-4f8c-ad59-7e0e3aba39e4",
"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 Jira, 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": "86ca6ebc-3bef-43ab-addd-99030e3aea32",
"text": "Call Jira",
"x": 512,
"y": 720,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://{yoursite}.atlassian.net/rest/api/3/issue",
"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": "a344e35e-c8fc-40a5-a61b-b88d51613fb2",
"start": {
"id": "3fcbda46-7b75-495a-a547-1a28bd118bd4",
"type": "output"
},
"end": {
"id": "afc45d99-04f6-4789-a27b-a2e23b697096",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "31395bd6-eda9-423a-abd5-13b4032d8450",
"start": {
"id": "afc45d99-04f6-4789-a27b-a2e23b697096",
"type": "output"
},
"end": {
"id": "1393b62a-9a32-4f8c-ad59-7e0e3aba39e4",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "8e0b321d-8d56-474f-a5f0-69605c033ade",
"start": {
"id": "1393b62a-9a32-4f8c-ad59-7e0e3aba39e4",
"type": "output"
},
"end": {
"id": "86ca6ebc-3bef-43ab-addd-99030e3aea32",
"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://{yoursite}.atlassian.net/rest/api/3/issue. - 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 Jira, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Google Drive to Jira
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Jira (one OAuth sign-in) and Google Drive (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-drive-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.
Google Drive and Jira — common questions
Can I connect Google Drive to Jira without writing code?
You can build it entirely from the canvas. Authorise Google Drive with one OAuth sign-in, Jira with one OAuth sign-in, then tell the agent what auto-summarise incoming docs should look like once Jira is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Google Drive to Jira automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles auto-summarise incoming docs the way a colleague would — reading the Google Drive context, judging it, then writing to Jira with the reasoning recorded.
Does my Google Drive and Jira data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Drive or Jira tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Google Drive and Jira run leave behind?
Every run is recorded end to end — the Google Drive items examined, the decision and its reasoning, the resulting Jira write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
