Connect Linear to Formsite
When something happens in Linear, Notis takes the next step in Formsite. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Linear to Formsite
Check Formsite inventory for new Linear work
When a Linear issue arrives, check available Formsite forms and report the closest fit or that no relevant form exists.
Review Formsite questions for a new request
When a Linear issue raises a form change or review, retrieve the relevant Formsite questions and summarize the current structure for the issue.
Add Formsite status context when work changes
When a Linear issue changes, retrieve details for the relevant Formsite form and report its name, state, publishing information, and result count.
Check latest Formsite responses from a Linear comment
When a comment asks about feedback or submissions, retrieve the latest relevant Formsite results and summarize the requested signal.
Recheck form questions after issue changes
When an issue's properties change, retrieve the relevant Formsite items and summarize the form structure to help reassess scope.
Give each new project a Formsite catalog overview
When a Linear project is created, list Formsite forms and report any that appear relevant to the project context.
Check form readiness when project properties change
When a project status, lead, date, or other property changes, retrieve the relevant Formsite form details and report its current state.
Add a latest feedback pulse to project updates
When a Linear project update is posted, retrieve the latest relevant Formsite results and report a concise feedback pulse.
Check Formsite webhook setup from a Linear comment
When a public-team comment raises a form delivery or integration concern, retrieve the relevant Formsite webhook configurations and summarize them.
Supported Triggers and Actions
Notis builds workflows that link Linear to Formsite. A trigger fires from one place; an action lands in another.
Linear triggers
Formsite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Form Details
This tool retrieves detailed information about a specific form in formsite. it provides comprehensive details including the form's internal description, directory identifier, name, publishing information (embed code and form link), current state (e.g., "open"), and statistics (file size and number of results).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Form Items
This tool retrieves all items (questions) for a specific form using the get https://{server}.formsite.com/api/v2/{user dir}/forms/{form dir}/items endpoint. it is an independent action that only requires the form directory (obtainable via formsite list all forms) to retrieve the structure and details such as item ids, question types, text, answer choices, required status, and other properties.
Comment Received Trigger
Triggered when a comment is received.
Get Form Results
This tool retrieves the latest form results from a specified formsite form. it uses the get https://{server}.formsite.com/api/v2/results/latest endpoint to fetch results independently, handling required parameters such as form id, limit, page, and sort direction without referring to external resource ids.
Issue Created Trigger
Triggered when a new issue is created.
Get Form Webhooks
This tool retrieves all webhooks configured for a specific form in formsite. it uses the get https://{server}.formsite.com/api/v2/{user dir}/forms/{form dir}/webhooks endpoint to fetch webhook configurations, including url, status, settings, and triggers.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
List All Forms
This tool retrieves a list of all forms in the user's formsite account. it provides essential information such as form id, form name, form directory, creation date, last modified date, status, access level, and other metadata. it serves as a foundational tool for further operations.
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).
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Linear and Formsite
Connect any two apps with Notis in the middle.
Linear and Formsite, 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 Formsite.