Connect Linear to Engage
When something happens in Linear, Notis takes the next step in Engage. 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 Engage
Create an Engage profile from a support issue
When a new Linear issue captures a customer support need, create or update the matching Engage user so the context is ready for follow-up.
Keep customer attributes current when issue priority changes
When a Linear issue changes, have Notis update the relevant Engage user attributes to reflect the latest customer context or urgency.
Put customers with new issues on a follow-up list
When a new Linear issue identifies a customer who needs attention, subscribe that customer to the appropriate Engage list for organized follow-up.
Record customer comments as Engage events
When a comment arrives on a Linear issue, record a meaningful customer interaction in Engage so engagement history has the context.
Remove resolved customers from a follow-up list
When a relevant Linear issue changes to a resolved state, have Notis update the customer's Engage list status to reflect that follow-up is complete.
Create a customer list for a new project
When a Linear project is created, create a corresponding Engage list for the customers or accounts connected to that initiative.
Keep account context current as projects change
When a Linear project's properties change, update the relevant Engage account attributes so customer-facing context can keep pace.
Log project updates as customer engagement events
When a Linear project update is posted, record a relevant event for the associated Engage customer or account to preserve a timeline of progress.
Reflect private-team relationship changes in account roles
When a comment in a private Linear team signals a customer relationship change, update the relevant customer's role within their Engage account.
Supported Triggers and Actions
Notis builds workflows that link Linear to Engage. A trigger fires from one place; an action lands in another.
Linear triggers
Engage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Customer to Accounts
Tool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Lists
Tool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.
Comment Received Trigger
Triggered when a comment is received.
Archive List
Tool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.
Issue Created Trigger
Triggered when a new issue is created.
Archive User
Tool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events for the user will be stopped, but all messages, logs, and related data will be preserved.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Convert User Type
Tool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.
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 List
Tool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create User
Tool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Delete Subscriber From List
Tool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.
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 Engage
Connect any two apps with Notis in the middle.
Linear and Engage, 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 Engage.