Surface Customer Context on New Issues
Automatically list existing Botpress conversations when a new Linear issue is created, preventing duplicate problem-solving.
Connect Linear to Botpress
When something happens in Linear, Notis takes the next step in Botpress. 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
Permanently deletes a file from a bot’s storage; this cannot be undone.
Examples
Ways Notis can move work from Linear to Botpress
Detect Bot Problems During Team Discussion
List Botpress bot issues whenever a comment is received on a Linear issue, surfacing technical blockers before solutions are finalized.
Verify Workspace Setup on New Projects
List Botpress workspaces whenever a new Linear project is created, ensuring bot automation is in place before work begins.
Track Customer Sentiment on Project Updates
Gather Botpress conversations when project status updates are posted, capturing asynchronous customer feedback without manual searching.
Sync Issue Priority to Bot Issues
List Botpress issues whenever Linear issue properties change, ensuring priority shifts are reflected in bot error tracking.
Preserve Private Team Context in Bot
List bot file tags when private team issues are created, verifying the bot has current context before private team work proceeds.
Connect Conversations to Issue Updates
List Botpress conversations whenever a Linear issue is updated, linking customer feedback to issue progress.
Verify Workspace Coverage on Public Issues
List public Botpress workspaces when public team issues are created, ensuring customer-facing problems are covered by bot automation.
Check Bot Tag Alignment on Label Changes
List bot file tag values when issue properties change, ensuring Botpress file tagging schema matches updated issue labels.
Supported Triggers and Actions
Notis builds workflows that link Linear to Botpress. A trigger fires from one place; an action lands in another.
Linear triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Delete File
Permanently deletes a file from a bot’s storage; this cannot be undone.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Break Down Workspace Usage By Bot
Breaks down workspace usage by bot, including invocations, storage, and AI spending.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Get Account
Retrieves details of the authenticated account.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES
Charges specified unpaid invoices for a Botpress workspace.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
LIST_BOT_ISSUES
Lists issues associated with a bot.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Check Handle Availability
Checks whether a workspace handle is available and suggests alternatives if it is taken.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
LIST_CONVERSATIONS
Lists conversations so you can retrieve chat threads.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
BOTPRESS_CREATE_ADMIN_INTEGRATION
Creates an integration in a workspace.
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 Botpress
Connect any two apps with Notis in the middle.
Linear and Botpress, 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 Botpress.