Start form submissions with known issue context
Put useful context in place before someone fills out the next form.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Prepopulate Formdesk Fields
Tool to prepopulate form fields. Use when loading default, parameter-based, lookup, import, or webservice-provided values before displaying a form.
Why this helps
People are often asked to repeat details already recorded in an issue, creating extra effort and inconsistent answers.
- Cuts down on repeated information entry.
- Helps submissions arrive with useful context.
- Makes the next step easier to start.
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 ask Notis for it in plain language.
- 3Tell Notis which status change should prepopulate which relevant Formdesk form fields using the issue context.
- 4Choose the Linear Issue Updated trigger and a channel for run reports.
- 5Test with a real issue update and verify the prepopulated values.
Questions about this workflow
Does prepopulation submit the form?
No. Prepopulation prepares values before the form is displayed; it does not create a submission.
Can this run for a specific status?
Describe the target status in the prompt.
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.