Bring Formcarry context into changing Linear work
When the shape of an issue changes, let Notis retrieve form submissions that may clarify the request behind it.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Retrieve Form Submissions
Tool to retrieve a list of submissions for a specific form identified by its id. supports pagination to navigate through large sets of submissions.
Why this helps
Issue details evolve, while useful customer context remains tucked away in a separate form inbox.
- Use issue updates as a cue to revisit customer-submitted context.
- Reduce repeated switching between the tracker and a form dashboard.
- Keep changing work connected to its intake trail.
Setup
Build it in a few focused steps.
- 1Connect Linear and Formcarry to Notis once through the portal.
- 2Create an automation in the portal or tell Notis what review to perform.
- 3Write a single plain-language prompt asking Notis to retrieve submissions from the relevant Formcarry form when a Linear issue changes and report useful context.
- 4Choose the Linear Issue Updated trigger and the channel for run reports.
- 5Test with one real issue update and inspect the retrieved results.
Questions about this workflow
What counts as an issue update?
The trigger fires when a Linear issue is updated, such as when its labels or status change.
Can the action fetch a single matching submission?
The available action retrieves a list of submissions for a specified form and supports pagination.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Formcarry. A trigger fires from one place; an action lands in another.
Linear triggers
Formcarry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve Form Submissions
Tool to retrieve a list of submissions for a specific form identified by its id. supports pagination to navigate through large sets of submissions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Comment Received Trigger
Triggered when a comment is received.
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 Formcarry, 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 Formcarry.