Connect Linear to Fomo
When something happens in Linear, Notis takes the next step in Fomo. 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 Fomo
Review Fomo events when Linear work begins
When a Linear issue is created, retrieve recent Fomo events so you can check customer activity before deciding what work needs attention.
Check Fomo activity after an issue changes
When a Linear issue changes, retrieve Fomo events so you can reassess the work with recent customer activity in view.
Bring Fomo activity into comment follow-up
When a Linear comment arrives, retrieve Fomo events to help you respond with customer activity in mind.
Review Fomo activity at project kickoff
When a Linear project is created, retrieve Fomo events to help ground kickoff planning in recent customer activity.
Review Fomo activity after project changes
When Linear project properties change, retrieve Fomo events so you can reassess plans with recent activity in view.
Add Fomo context to project status updates
When a Linear project status update is posted, retrieve Fomo events to support a grounded review of progress and customer activity.
Review Fomo activity for private team issues
When a private team issue is created, retrieve Fomo events to give your internal triage a customer activity reference.
Recheck Fomo activity after private issue changes
When a private team issue's properties change, retrieve Fomo events for an updated view during internal follow-up.
Review Fomo activity after private comments
When a comment is posted on a private team issue, retrieve Fomo events to add customer activity context to internal discussion.
Supported Triggers and Actions
Notis builds workflows that link Linear to Fomo. A trigger fires from one place; an action lands in another.
Linear triggers
Fomo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Fomo Events
This tool retrieves a list of all events from your fomo application. the endpoint is self-contained and doesn't require any external resource ids, making it independently executable. authentication is handled through the api token.
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).
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 Fomo
Connect any two apps with Notis in the middle.
Linear and Fomo, 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 Fomo.