Keep compliance task ownership aligned in Linear
Reflect ownership changes in the Linear issue connected to a 21risk task.
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
Ownership changes recorded in one system can leave the team's Linear issue assigned to the wrong person.
- Keep the related Linear issue aligned with available ownership updates.
- Reduce manual checks after a compliance owner changes.
- Make responsibility easier to see where the team manages work.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Linear once in Notis.
- 2Create an automation with one instruction: when incoming 21risk data reports an ownership change and identifies the related Linear issue and a valid Linear user, update that issue's assignee.
- 3Choose the webhook trigger and send ownership updates from the relevant 21risk process.
- 4Choose where Notis should send run reports.
- 5Test with one real ownership change and confirm the issue assignee.
Questions about this workflow
Does 21risk automatically provide a Linear user id?
Not necessarily. The incoming data or instruction must make the intended Linear user identifiable. Check the test run before relying on automatic assignment.
What happens if no related issue is identified?
The instruction should only update issues that can be reliably identified from the incoming data.
Can the automation change other issue fields too?
This workflow is intended to update the assignee. Include other changes only when the update data supports them and the outcome is clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Linear. A trigger fires from one place; an action lands in another.
21risk triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
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.
21risk and Linear, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Linear.