Bring form context to project updates
A project update that raises a form need can prompt a fresh lookup of available Fillout forms.
Trigger
Project Update Posted
Fires when a project status update is posted on the Linear project's Updates tab. Covers projects in both public and private teams — polls with the connected user's token.
Action
Get forms
Tool to retrieve a list of all forms in your account. use when you need to list your forms after authenticating with fillout.
Why this helps
A form need mentioned in a status update can be forgotten when attention moves to the next project task.
- Surface available forms when an update raises a relevant need.
- Keep the form lookup close to the project status context.
- Help reduce dropped follow-up from project communications.
Setup
Build it in a few focused steps.
- 1Connect Linear and Fillout forms to Notis once in the portal.
- 2Create an automation with a plain-language prompt to retrieve the Fillout form list when a project update requests a form reference.
- 3Select the Linear Project Update Posted trigger.
- 4Choose a channel for run reports and test with an update that mentions a form need.
Questions about this workflow
Does this read or summarize the update?
The trigger is a posted project update. The action retrieves the Fillout form list for the described request.
Can the form list be sent to a project channel automatically?
Choose a channel for Notis run reports. The available Fillout action itself only retrieves forms.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Fillout forms. A trigger fires from one place; an action lands in another.
Linear triggers
Fillout forms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authorize OAuth
Tool to initiate the oauth authorization process for third-party applications. use when you need to generate the url to redirect your users to the fillout consent page.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get forms
Tool to retrieve a list of all forms in your account. use when you need to list your forms after authenticating with fillout.
Comment Received Trigger
Triggered when a comment is received.
Invalidate Access Token
Tool to revoke an existing oauth access token. use when the user logs out or you need to programmatically invalidate a token after deauthorization. example: "invalidate token abcdefg123456". this endpoint does not return a json body. successful calls return http 200 or 204.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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 Fillout forms, 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 Fillout forms.