Give new investigation issues a ready-to-use sandbox
When a Linear issue requests an investigation or reproducible example, create a fresh E2B sandbox so the work can start with an isolated environment.
Connect Linear to E2b
When something happens in Linear, Notis takes the next step in E2b. 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
Connect to an existing sandbox and view its details.
Examples
Ways Notis can move work from Linear to E2b
Pause the sandbox when work becomes blocked
When a Linear issue is marked blocked, have Notis pause its associated E2B sandbox to preserve the working state while reducing unnecessary active runtime.
Keep an active issue sandbox available
When a Linear issue moves into active work, refresh the relevant E2B sandbox to extend its time to live and avoid losing momentum to an expired environment.
Check sandbox readiness for environment requests
When an issue asks for an existing sandbox to be checked, retrieve its E2B details and report the current state so the next step is clear.
Retrieve sandbox logs when an issue requests debugging
When a Linear comment asks for sandbox logs, retrieve the relevant E2B output and report it for review so debugging can continue with less searching.
Check sandbox resource use for a resource-related issue
When an issue update flags resource pressure on a sandbox, retrieve its metrics so you can inspect usage with the issue context in mind.
Reconnect to a sandbox when an issue resumes
When a new Linear issue signals that paused work is resuming, reconnect to the existing E2B sandbox to retrieve its details and extend its TTL.
Clean up a sandbox when its issue is complete
When a Linear issue is marked complete and its sandbox is no longer needed, delete that sandbox to remove lingering environments from your active list.
Set a deliberate timeout for temporary sandboxes
When a new issue calls for a bounded experiment, set its sandbox timeout so the temporary environment has a defined lifetime.
Supported Triggers and Actions
Notis builds workflows that link Linear to E2b. A trigger fires from one place; an action lands in another.
Linear triggers
E2b actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Connect to Sandbox
Connect to an existing sandbox and view its details.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Create Template
Create a template for launching sandbox environments.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Create Webhook
Register a webhook for sandbox lifecycle notifications.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
Delete Sandbox
Terminate and permanently delete a sandbox; it cannot be resumed.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Delete Webhook
Unregister a webhook and stop its lifecycle notifications.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Delete Template
Permanently deletes a template; running or paused sandboxes must not use it.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Check API Health
Check whether the service is operational.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
Get Sandbox
View details about a sandbox.
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 E2b
Connect any two apps with Notis in the middle.
Linear and E2b, 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 E2b.