Turn new Linear issues into Canny feedback posts
When a new Linear issue captures a customer request, create a Canny post with the relevant context so feedback has a home outside the engineering queue.
Connect Linear to Canny
When something happens in Linear, Notis takes the next step in Canny. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new comment is received.
Do this · Action
Adds an existing tag to a post.
Examples
Ways Notis can move work from Linear to Canny
Carry Linear discussion into Canny feedback threads
When a Linear comment adds a meaningful response to a customer request, add a comment to the corresponding Canny post to keep its discussion current.
Update Canny status when Linear work changes
When a Linear issue's status changes, update the matching Canny post's workflow status where the issue signals a clear customer-facing progress change.
Use Linear labels to categorize Canny feedback
When an issue receives a relevant Linear label, apply the corresponding existing tag to its Canny post for easier feedback organization.
Turn Linear project updates into Canny changelog entries
When a Linear project update describes a customer-facing release or improvement, create a Canny changelog entry with the relevant announcement details.
Refresh Canny timelines from Linear project changes
When a Linear project target date or other delivery detail changes, update the matching Canny post's ETA when the change is relevant to a published customer timeline.
Create a Canny tag for a new Linear project theme
When a new Linear project establishes a meaningful customer-facing product theme, create a corresponding Canny tag to help organize related feedback.
Keep Canny user profiles aligned with issue contacts
When a Linear issue update identifies a changed customer contact or owner detail, update the associated Canny user profile when the information is appropriate and available.
Record product demand from prioritized Linear issues
When a Linear issue is marked as a confirmed customer request, create a Canny post or record the relevant demand on its corresponding post according to the available feedback context.
Supported Triggers and Actions
Notis builds workflows that link Linear to Canny. A trigger fires from one place; an action lands in another.
Linear triggers
Canny actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Add Post Tag
Adds an existing tag to a post.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Delete User
Deletes a user and their comments and votes; some posts may also be removed.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Change Post Status
Changes a post’s status and can notify voters.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
Create Changelog Entry
Creates a changelog entry and can publish it or notify users.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Create Comment
Posts a new comment on a post.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Create or Update User
Creates or updates a Canny user; an admin's email, name, and avatar cannot be changed via the API.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Create Post
Creates a feature request or feedback post on a board.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
Create Tag
Creates a tag for categorizing posts.
ActionInstant
Trigger Types
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
New Notion pageStripe chargeCalendar event
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.
Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
Why AI automation
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.
Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use
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:
TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability
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
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
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.
Related pairs
More ways to connect Linear and Canny
Connect any two apps with Notis in the middle.
Linear and Canny, or any other combination from 1,500+ 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 Canny.