Connect Linear to Fly
When something happens in Linear, Notis takes the next step in Fly. 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 Fly
Validate Fly configuration when a deployment issue is filed
When a Linear issue describes a planned Fly deployment or config change, validate the relevant Fly app configuration and report whether it is ready for review.
Refresh Fly app details when release scope changes
When a Linear issue update signals a release scope or target-app change, retrieve the relevant Fly app details and summarize what is currently configured.
Check Fly app inventory when a service issue changes
When a Linear update identifies a new or renamed service, list the Fly apps in the relevant organization and summarize whether the expected app appears.
Confirm Fly region support for new deployment work
When a Linear issue proposes a region-specific deployment, retrieve available Fly regions and summarize whether the requested location is available.
Review Fly placement options after capacity changes
When a Linear update changes capacity requirements, retrieve Fly placement recommendations and summarize the regions that fit the stated constraints.
Check the latest Fly image for a release issue
When a Linear issue calls for a release image check, retrieve the latest image details and report its tag and digest for review.
Refresh the Fly image tag when a release version changes
When a Linear issue update changes a release version or image reference, retrieve the latest Fly image tag and include it in the run report.
Apply an approved Fly Apps V2 default decision
When a Linear issue records an explicit platform decision for new apps, set the organization's Fly Apps V2 default according to that decision.
Create a Fly health check from an uptime issue
When a Linear issue requests monitoring for a specific app endpoint, create a Fly health check job and report the setup outcome.
Supported Triggers and Actions
Notis builds workflows that link Linear to Fly. A trigger fires from one place; an action lands in another.
Linear triggers
Fly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add WireGuard Peer
Tool to add a WireGuard peer connection to a Fly.io organization for private network access. Use when setting up VPN access or private networking between your infrastructure and Fly.io.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check App Name Availability
Tool to validate an app name for Fly.io app creation. Use when you need to check if a proposed app name is available before attempting to create a new app. Returns availability status via GraphQL query.
Comment Received Trigger
Triggered when a comment is received.
Check Jobs
Execute GraphQL queries against the Fly.io checkJobs endpoint. Retrieves check jobs with their schedules, URLs, and configuration. Supports pagination via first/last/after/before parameters. Returns both data and errors for flexible error handling.
Issue Created Trigger
Triggered when a new issue is created.
Check User Only Token
Check whether the authentication token only allows user access. Returns false if the token allows organization access, true if it only allows user access.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Health Check Job
Tool to create a health check job for monitoring application endpoints in Fly.io. Use when you need to set up automated health monitoring for a URL from multiple geographic locations.
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).
Create Check Job Run
Triggers a run of an existing health check job on Fly.io. Use when you need to manually trigger a health check for monitoring or testing purposes.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create Delegated WireGuard Token
Tool to create a delegated WireGuard token for peer management in a Fly.io organization. Use when you need to generate a token for managing WireGuard peers with delegated access.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Third-Party Configuration
Tool to create a third-party service configuration for discharging macaroon caveats. Use when you need to configure external authorization services for Fly.io token validation.
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 Fly
Connect any two apps with Notis in the middle.
Linear and Fly, 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 Fly.