Update Linear Issues from Any External System
Your billing tool, email, or custom software wants to update a Linear issue. Send Notis a webhook request and the issue updates instantly.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update issue
Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.
Why this helps
Many tools and systems generate information that should update Linear, but they have no direct connection. Neurodivergent teams manually sync status changes, leading to delays and forgotten updates.
- Connects external tools to Linear without custom code
- Status updates happen instantly
- Reduces manual status changes
- Keeps Linear current with external systems
Setup
Build it in a few focused steps.
- 1Connect Linear to Notis.
- 2Set up a webhook trigger and get your Notis URL.
- 3Configure your external tool to send data to Notis when status changes (check your tool's webhook or API docs).
- 4Tell Notis 'When you receive a webhook, update the Linear issue with the provided status and details.'
- 5Test by triggering an event in your external tool and confirming the Linear issue updates.
Questions about this workflow
How do I configure my external tool to send webhooks to Notis?
Check your tool's webhook or API docs for the endpoint. You'll typically add a webhook URL that points to Notis. Notis will provide that URL when you set up the automation.
What data can I pass through the webhook?
Any data your tool can send: status updates, priority changes, assignee changes, custom fields, etc. Tell Notis how to map that data to Linear fields.
Can I update multiple issues with one webhook?
Yes. Tell Notis 'if the webhook includes multiple issue ids, update all of them' and it will apply the change to each.
When this happens · Trigger
Do this · Action
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.
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.