Project Changes Trigger Automatic Documentation Updates
Project scope just shifted? Notis auto-creates an updated scope form capturing new goals and reassigning ownership instantly.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls 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
Project scope changes but old documentation lingers. Team operates on stale goals while actual scope lives only in conversations.
- Keep project documentation current as scope evolves
- Smooth leadership transitions with handoff forms
- Build audit trail of scope decisions
- Prevent team confusion from outdated project docs
Setup
Build it in a few focused steps.
- 1Connect Linear and Byteforms to Notis.
- 2Ask Notis: 'When a Linear project's lead, status, or priority changes, create an updated scope form asking for new goals and success metrics' or use the portal.
- 3Set the trigger to 'Project Properties Updated'.
- 4Select your notification channel.
- 5Change a project's lead or status and verify the update form appears in Byteforms.
Questions about this workflow
Should the form auto-compare new scope to old scope?
Yes. Tell Notis to include a 'what changed from the original plan?' section that highlights scope drift.
Can the form ask why the project lead is changing?
Absolutely. Include a question like 'What prompted this leadership change?' to capture context.
What if the project status changed but nothing else did?
You can tell Notis to skip form creation for minor status changes, or only trigger on significant scope shifts.
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.