Make Linear blockers harder to overlook
Create a dependable follow-up record when progress stops.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Create Formdesk Entry
Tool to submit a new entry to a Formdesk form. Use after collecting all form field values to send a new entry for a specific formId. Example: "Submit entry to form 12345 with first_name='Bob', email='bob@example.com'."
Why this helps
Blocked work can sit unnoticed when attention is divided across projects and conversations.
- Makes stalled work visible in a dedicated record.
- Preserves blocker context for follow-up.
- Reduces manual checking of issue status.
Setup
Build it in a few focused steps.
- 1Connect Linear and Formdesk to Notis once through the portal.
- 2Create an automation in the portal or describe it to Notis in a chat.
- 3Ask Notis to create a Formdesk entry when an issue becomes blocked, including why it is blocked and its owner when available.
- 4Choose the Linear Issue Updated trigger and a channel for run reports.
- 5Test by changing one issue to blocked and reviewing the entry.
Questions about this workflow
Can this run only when an issue becomes blocked?
Describe the blocked status condition in the plain-language prompt so Notis can focus on that change.
What should the Formdesk entry contain?
Tell Notis to include the issue context needed for your follow-up process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Formdesk. A trigger fires from one place; an action lands in another.
Linear triggers
Formdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Automatic Login
Tool to perform automatic login to Formdesk and retrieve an access token. Use when you need to authenticate with username and password.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Formdesk Entry
Tool to submit a new entry to a Formdesk form. Use after collecting all form field values to send a new entry for a specific formId. Example: "Submit entry to form 12345 with first_name='Bob', email='bob@example.com'."
Comment Received Trigger
Triggered when a comment is received.
Create Field
Tool to create a new field in a specific Formdesk form. Use after you have the formId and need to extend the form schema with an additional input.
Issue Created Trigger
Triggered when a new issue is created.
Create Visitor
Tool to add a new visitor to a specific Formdesk form. Use when you need to register a visitor's metadata (e.g., name, email) before submitting entries.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Formdesk Entry
Tool to delete a specific entry from a Formdesk form. Use after confirming the target entry exists.
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).
Delete Field in Formdesk
Tool to delete a specific field in a Formdesk form. Use after confirming formId and fieldId.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete Form in Formdesk
Tool to delete a specific form. Use when you need to permanently remove a form after confirming it's no longer needed.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Delete Visitor in Formdesk
Tool to delete a specific visitor in a Formdesk form. Use after confirming formId and visitorId.
Connect any two apps with Notis in the middle.
Linear and Formdesk, 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 Formdesk.