Document Incident Learnings Immediately as Issues Resolve
Incident just marked resolved? Notis auto-creates a postmortem form capturing what happened, why, and what's next to prevent recurrence.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Action
Create form
Tool to create a new form. use when you need to define and store a form structure.
Why this helps
Incidents get closed without systematic postmortem. Months later you're repeating the same mistakes because lessons weren't documented.
- Capture postmortem insights while incident is fresh
- Build searchable incident knowledge base over time
- Reduce repeat incidents by systemizing learnings
- Improve team resilience through documented patterns
Setup
Build it in a few focused steps.
- 1Connect your Linear workspace (with private teams) and Byteforms to Notis.
- 2Tell Notis: 'When an incident issue in my private team changes status to resolved, generate a postmortem form asking what caused the incident, what was tried to fix it, and what changes prevent recurrence' or use the portal.
- 3Set the trigger to 'Private Team Issue Properties Updated' (filtering for incident status changes).
- 4Choose your notification channel.
- 5Close a test incident and verify the postmortem form appears in Byteforms.
Questions about this workflow
Should the form ask the team to rate severity or impact retrospectively?
Yes. Include questions like 'On reflection, how bad was this actually?' to calibrate future response.
Can the form auto-populate incident details from Linear?
Absolutely. Notis can pre-fill incident name, duration, systems affected, and response timeline from the issue.
Who should complete the postmortem form?
Tell Notis to notify the incident lead and key responders so the team completes it while memory is fresh.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Byteforms. A trigger fires from one place; an action lands in another.
Linear triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
Comment Received Trigger
Triggered when a comment is received.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
Issue Created Trigger
Triggered when a new issue is created.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Byteforms, 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 Byteforms.