Connect Linear to Grafbase
When something happens in Linear, Notis takes the next step in Grafbase. 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 Grafbase
Check Grafbase keys when a credential request arrives
When a Linear issue requests a Grafbase credential, retrieve the project's API key inventory so the team can review what already exists before creating or sharing access.
Review Grafbase MCP servers after a Linear issue update
When an issue is updated with MCP configuration work, retrieve the Grafbase MCP server list to give the team a current view before continuing implementation.
Capture a schema registry snapshot when a Linear project starts
When a Linear project is created, list Grafbase schemas to provide a starting registry snapshot for planning the project's graph work.
Review schema check history when a project date changes
When a Linear project property changes, list Grafbase schema checks so the team can assess recent validation history alongside the revised plan.
Add schema check history to a project status update
When a Linear project status update is posted, retrieve Grafbase schema check history so technical status discussions can include validation context.
Fetch a Grafbase check result from a Linear comment
When a comment includes a Grafbase schema check ID, retrieve the result so the team can follow up without manually locating the check.
Retrieve subgraph SDL when a schema issue changes
When a Linear issue is updated to discuss a subgraph schema, retrieve that subgraph's SDL to make review and debugging more concrete.
List Grafbase subgraphs when federation work is filed
When a Linear issue is created for federation or graph planning, list Grafbase subgraphs so contributors can start with the available subgraph inventory.
Check configured extensions for a new Grafbase task
When a Linear issue is filed about Grafbase extensions, list configured extensions to provide a quick baseline for investigation or planning.
Supported Triggers and Actions
Notis builds workflows that link Linear to Grafbase. A trigger fires from one place; an action lands in another.
Linear triggers
Grafbase actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Grafbase API Key
Tool to delete an existing API key. Use after confirming the key ID to revoke access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Grafbase Audit Log
Tool to delete a specific Grafbase audit log entry. Note: As of current Grafbase public documentation, there is no documented API to delete audit logs programmatically. This action will attempt a best-effort REST DELETE to `/audit-logs/{id}` and, if unsupported or not found, it will gracefully fall back to validating connectivity with the GraphQL Management API and return a structured response instead of failing.
Comment Received Trigger
Triggered when a comment is received.
Delete Extension
Tool to delete an extension configuration. Use after confirming the extension_id to remove the extension.
Issue Created Trigger
Triggered when a new issue is created.
Delete MCP Server
Tool to delete a Grafbase MCP server configuration by its unique ID. Use after confirming the server ID to remove an existing MCP server.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Grafbase Schema
Tool to delete a Grafbase schema. Use when you need to remove a specific schema from the registry after confirming its ID.
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 Schema Check
Tool to delete a Grafbase schema check. Use when you need to remove a specific schema check by its ID after reviewing the registry.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Disable MCP server
Tool to disable the Model Context Protocol server. Use when you need to turn off MCP via API after it has been enabled.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Enable Grafbase MCP Server
Tool to enable the Model Context Protocol (MCP) server for a Grafbase project. Use when you need to activate MCP support; if the API endpoint is not supported, this returns guidance for enabling via configuration.
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 Grafbase
Connect any two apps with Notis in the middle.
Linear and Grafbase, 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 Grafbase.