Skip to content
ClickRuntime

Connect Google Drive to Jira

Drive holds the documents, and Jira holds the work that comes out of them. Connecting the two turns meeting transcripts into tasks, keeps incident evidence filed next to its ticket, and gives every new hire a ready folder alongside their onboarding tickets.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with Google Drive and Jira

Onboarding folders, meeting action items and incident evidence, linked between Google Drive and Jira. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Set up a Drive folder and Jira tickets for each new hire

For every new hire, a Drive folder with copies of your onboarding documents is created and shared, Jira onboarding tickets are opened, and Slack gets a summary.

See how it works
Every 15 minutesAI

Turn meeting transcripts in Drive into Jira tasks

When a meeting transcript is saved to your Drive folder, its action items become Jira tasks with owners and due dates, and Slack lists them.

See how it works
The moment it happens

Open an incident ticket and archive its evidence in Drive

Each reported incident opens a Jira ticket, its report is saved to your Drive incidents folder, and the ticket links to the file.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Google Drive and Jira, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Google Drive and Jira automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Google Drive and Jira in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

When a PDF lands in my Drive folder Client Briefs, have AI list the deliverables and create one Jira task per deliverable under a new epic named after the file.

When a Jira epic is created in project WEB, create a Drive folder with Design and Copy subfolders and add the folder link as a comment.

Use cases

Why people connect Google Drive and Jira

How the two apps work together

  • The automation checks a Drive folder for new or changed files every few minutes.
  • New files become Jira issues or comments, with the file name and link in the description.
  • Jira events, through webhooks or scheduled checks, can create Drive folders or documents and write their links back to the ticket.

  • Project folders for new epics

    Delivery teams create a Google Drive folder for each new Jira epic and add the folder link to the epic. Specs and designs have one home from day one.

  • Contracts and specs become tickets

    Agencies turn a new brief or statement of work saved in Drive into Jira tasks. AI pulls the deliverables out of the document.

  • Release documents archived

    Release managers export the list of tickets in a fix version to a document in Drive when the version is released. It serves as an audit record.

  • Review requests for new documents

    Legal and compliance teams open a Jira review task when a file is added to a Drive folder for review.

More apps

Google Drive, Jira and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Postmortem doc for each incident ticket

When a Jira issue of type Incident is resolved, create a postmortem Google Doc from my template in the Incidents folder and link it on the ticket.

New spec in Drive opens Jira and Slack

When a file is added to Drive folder Specs, create a Jira story with the link and post it in #product.

Drive meeting notes to Jira and Confluence

When meeting notes appear in my Drive folder, create Jira tasks for the action items and copy the notes to our Confluence space.

Setup

Connect Google Drive and Jira once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Google Drive

File storage

  1. At console.cloud.google.com, create a project and enable the Google Drive API.
  2. Set up the OAuth consent screen and add the scope https://www.googleapis.com/auth/drive.
  3. Create an OAuth client of type Web application with the redirect URI https://clickruntime.com/oauth/callback.
  4. In the ClickRuntime dashboard, open Connections, choose Google Drive and enter the client ID and secret, then connect.
  5. Prefer a service account? Under IAM & Admin → Service Accounts, create one and add a JSON key, share your folders or a Shared Drive with its email, and save the key as a secret on Connections & secrets.

Jira

Project management / Issue tracking

  1. Go to id.atlassian.com/manage-profile/security/api-tokens and choose Create API token. Atlassian sends a code to your email to confirm.
  2. Name the token, choose an expiry of 1 to 365 days, create it and copy it straight away. It can't be shown again.
  3. Note your site address, such as yoursite.atlassian.net, and the email of the Atlassian account that created the token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the email, token and site for Jira.

FAQ

Questions about connecting Google Drive and Jira

Which Drive folders does it use?
The ones you choose when you set it up, such as a Transcripts folder to watch or an Incidents folder to save into. Shared drives work too.
Are files shared with anyone automatically?
Only where the automation says so, such as a new hire's onboarding folder shared with them. Otherwise files keep the folder's existing sharing.
Does the Jira ticket link to the Drive file?
Yes. Each ticket created includes a link to the related Drive file or folder.
Which Google account does it use?
The Google account you connect in your ClickRuntime dashboard. Files are created as that account.
Can it read the contents of Drive files?
Yes, for Google Docs, text files and PDFs the script can read the text, and built-in AI can summarize it or pull out tasks.
Does it attach files to Jira or link them?
Either. A link keeps one copy in Drive; attaching uploads a copy to the Jira issue.
Can it handle files that already exist?
The first run can skip existing files or process them all. Later runs only handle files added after that.

Related pages

Keep exploring

Tell your assistant what Google Drive and Jira should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude