Turn Google Docs Comments into Jira Tasks
Feedback stays visible. Every comment in your Google Docs becomes a trackable Jira task, keeping nothing in thread limbo.
Trigger
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Action
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Why this helps
Team feedback on shared Google Docs gets lost in comment threads and notification noise, forcing manual transcription into Jira tasks.
- Feedback automatically tracked as actionable tasks
- No more re-reading comment threads to create tasks
- Reduce context-switching between Docs and Jira
- Keep all feedback in one searchable place
- Transparent handoff from review to execution
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Jira to Notis (one-time setup in the portal or by asking Notis).
- 2Create a new automation and describe what you want: 'When someone adds a comment to my Google Docs, create a Jira task with the comment text.'
- 3Select 'Comment Added (Docs)' as your trigger and choose the Slack or email channel where Notis reports each run.
- 4Test with a real Google Doc: have a colleague add a comment and watch the task appear in Jira within seconds.
Questions about this workflow
Can I customize which Google Docs trigger this automation?
Yes. Notis lets you apply this to all your Docs, a specific folder, or docs matching certain keywords. Just include that in your plain-language instruction.
What if I want the task title to include the commenter's name?
Notis reads comment metadata automatically, including the author and timestamp. Just mention in your instruction that you want the commenter's name included.
Do duplicate comments create duplicate tasks?
No. Notis tracks which comments it has seen, so edits to existing comments won't spawn new tasks unless you have the automation set to regenerate.
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.