Connect Linear to Kanbanize
When something happens in Linear, Notis takes the next step in Kanbanize. 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 Kanbanize
Carry new Linear issue context into Kanbanize
When an issue is created in Linear, find its matching Kanbanize card and add a concise comment with the issue link, summary, and useful context so the team does not have to switch tools to catch up.
Surface Linear priority changes on the board
When a Linear issue changes, identify whether its priority changed and, if so, add a short comment to its matching Kanbanize card with the new priority and source link.
Block Kanbanize work when Linear reports a blocker
When a Linear issue is updated to indicate it is blocked, find the corresponding Kanbanize card and set its block reason to the agreed blocker category, using the issue details to make the reason clear.
Carry Linear decisions to Kanbanize
When a comment arrives on a Linear issue, identify comments that state a decision or change in direction and add a brief, source-linked summary to the matching Kanbanize card.
Add Linear project kickoff context to Kanbanize
When a Linear project is created, locate the related Kanbanize initiative card and add a comment with the project link and the purpose stated in Linear.
Surface Linear target date changes
When a Linear project's target date changes, find the related Kanbanize initiative card and add a comment with the revised date and project link.
Bring project status updates to Kanbanize
When a status update is posted on a Linear project, find the corresponding Kanbanize initiative card and comment with a concise summary, status, and link to the update.
Check ownership visibility for new issue work
When a Linear issue is created, find its corresponding Kanbanize card and check whether the responsible user is already watching it. Use the run report to surface a missing watcher for follow-up.
Mark ownership gaps on Kanbanize
When a Linear issue update removes or changes its assignee to an unassigned state, find the corresponding Kanbanize card and apply an agreed block reason to flag that ownership needs attention.
Supported Triggers and Actions
Notis builds workflows that link Linear to Kanbanize. A trigger fires from one place; an action lands in another.
Linear triggers
Kanbanize actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a card
Tool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Board Milestone
Tool to check if a milestone is available on the specified board. Use when you need to verify milestone existence on a specific board. Returns True if the milestone is available (HTTP 204), False if not found (HTTP 404).
Comment Received Trigger
Triggered when a comment is received.
Check User Is Card Watcher
Tool to check if a user is a watcher of a specific card. Use when you need to verify if a user is watching a card.
Issue Created Trigger
Triggered when a new issue is created.
Delete Board
Tool to delete a board by its ID. Use when you need to permanently remove a board from Kanbanize. Note: The board must be archived before deletion.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Card
Tool to delete a card from the Kanbanize board. Use when you need to permanently remove a card and all its associated data from the board.
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 Tag
Tool to delete a tag from Kanbanize. Use when removing a tag and optionally replacing it with another tag for all affected cards.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete Workflow
Tool to delete a workflow for the specified board. Use when you need to permanently remove a workflow from a board.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Board Block Reasons
Tool to get a list of block reasons available on a board. Use when you need to retrieve available block reasons for a specific board.
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 Kanbanize
Connect any two apps with Notis in the middle.
Linear and Kanbanize, 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 Kanbanize.