Connect 
Google Drive and 
Linear to power automations.
Trigger from one app, act on another, with a thinking brain in the middle. Build it in plain English. Approve from your phone.
When this happens · Trigger
Do this · Action
Most used workflows for Google Drive + Linear
Auto-Create Linear Issues from Google Drive Files
Every new Google Drive file automatically becomes a Linear issue, eliminating the friction of manual ticket creation.
Turn Google Docs Comments into Linear Issues
When collaborators comment on Google Docs, Notis converts the conversation into a Linear issue so feedback doesn't get buried.
Create Linear Issues When Files Are Shared
Automatically track file sharing as Linear issues. Know instantly when collaboration expands and ensure shared files get appropriate attention.
Update Linear Issues When Google Drive Files Change
Sync file updates to Linear by automatically updating related issues, keeping your issue description in sync with the latest file state.
Add Google Docs Comments as Linear Issue Comments
When collaborators comment on Google Docs, Notis automatically posts those comments to the related Linear issue, keeping all feedback in one place.
Daily Batch: Convert Recent Google Drive Files to Linear Issues
Every day at a set time, Notis reviews new Google Drive files from the past 24 hours and creates Linear issues in bulk, reducing daily friction.
Convert Research Files to Linear Issues Automatically
When new files matching a research query appear in Google Drive, Notis creates Linear issues so research findings surface as actionable work items.
Auto-Label Linear Issues from Google Docs Comment Context
When feedback is added via comments in Google Docs, Notis automatically applies relevant labels to the matching Linear issue for better organization.
Archive Linear Issues When Files Are Deleted
When a Google Drive file is deleted or trashed, Notis automatically archives the related Linear issue so your tracker stays clean.
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Linear. A trigger fires from one place; an action lands in another.
Google Drive triggers
Linear actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
File Created
Triggers when a new file is created in Google Drive.
Create a comment
Creates a new comment on a specified linear issue.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
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.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
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``.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it trough Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Google Drive and Linear
Connect any two apps with Notis in the middle.
Not just Google Drive and Linear. 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 Linear.