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
Do this · Action
Ways Notis can move work from Linear to E2b
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.
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.
Connect to Sandbox
Tool to connect to an existing E2B sandbox and retrieve its details. Use when you need to reconnect to a sandbox from different environments or resume a paused sandbox. The TTL is extended upon connection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Template
Tool to create a new E2B template with specified configuration. Use when you need to define a new sandbox template that can be used to spawn sandbox environments.
Comment Received Trigger
Triggered when a comment is received.
Create Webhook
Tool to register a new webhook to receive sandbox lifecycle events for the team. Use when you need to set up notifications for sandbox lifecycle events such as creation, updates, or termination.
Issue Created Trigger
Triggered when a new issue is created.
Delete Sandbox
Tool to terminate and permanently delete a running E2B sandbox instance. Use when you need to kill a sandbox that is no longer needed. Once terminated, the sandbox cannot be resumed.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Webhook
Tool to unregister a webhook and stop receiving lifecycle events. Use when you need to remove a webhook that is no longer needed or to clean up webhook registrations.
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).
Check API Health
Tool to check the health status of the E2B API. Use when you need to verify that the API service is operational and accessible.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Sandbox
Tool to retrieve detailed information about a specific sandbox by its ID. Use when you need to check sandbox status, metadata, or configuration details.
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 Sandbox Logs
Tool to retrieve logs from a specific E2B sandbox instance. Use when you need to debug or monitor sandbox execution by viewing its console output and system logs.
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 E2b
Connect any two apps with Notis in the middle.
Linear and E2b, 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 E2b.