Convert incoming webhooks into Linear issues
Requests that arrive by form or from a custom backend usually wait for someone to transcribe them. Notis catches the webhook and opens a Linear issue right away, so intake becomes tracked work without a human relay.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Requests that live in an inbox or a form until someone copies them into Linear are exactly the ones that slip through on a busy day.
- Incoming requests become Linear issues the instant they arrive.
- You skip the transcription step that so often gets deferred and forgotten.
- Any tool that can send an HTTP request can feed your Linear backlog.
Setup
Build it in a few focused steps.
- 1Connect Linear to Notis one time in the portal.
- 2Ask Notis for your portal link and start a New Automation, or describe it to Notis in plain language.
- 3State the outcome in one line, for example: When my intake webhook fires, create a Linear issue from the request details.
- 4Choose the incoming webhook as the trigger and point your form or backend at the address Notis gives you.
- 5Pick a report channel and test by sending one real submission through the webhook.
Questions about this workflow
What can send the webhook?
Anything that can make an HTTP request, such as a form tool, a script, or your own backend.
Do I need to format the payload a certain way?
Notis reads the incoming data and interprets it based on your instruction, so you do not build field maps.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Linear. A trigger fires from one place; an action lands in another.
Jira triggers
Linear actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
New Project
Triggered when a new project is added in Jira
Create a comment
Creates a new comment on a specified linear issue.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
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 Jira 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.