Sync Google Drive Updates to Jira Automatically
Document updates trigger Jira status changes. One source of truth for project progress.
Trigger
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
Updating a Google Drive document doesn't notify anyone in Jira, leaving tickets stale and making it hard to know if work is actually progressing.
- Status updates happen automatically when docs change
- Clearer project progress visibility
- No more stale Jira tickets
- Reduce status check-in meetings
- Automatic audit trail of work progress
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Jira to Notis.
- 2Create an automation: 'When a Google Drive file is updated, mark the related Jira ticket as In Progress' (or whatever status you prefer).
- 3Notis learns which Jira fields to update based on your plain-language instruction. Confirm the mapping.
- 4Test by editing a Google Drive file and checking that the Jira ticket status changes within seconds.
Questions about this workflow
Can I update multiple Jira fields based on one Drive file change?
Yes. For example: 'Mark it In Progress and add a comment saying the document was updated.' Notis will handle all of it.
What if the file is edited frequently? Will this spam Jira?
You can set a frequency threshold. For instance, 'only update Jira if the Drive file hasn't been modified in the last hour' to batch minor edits.
Can I see what changed in the Drive file from Jira?
Yes. Notis can add a comment to the Jira ticket with a summary of the changes or a link to the Drive file's revision history.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Jira. A trigger fires from one place; an action lands in another.
Google Drive triggers
Jira actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Add Attachment
Uploads and attaches a file to a jira issue.
File Created
Triggers when a new file is created in Google Drive.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Google Drive and Jira. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.