Connect Ably to E2b

When something happens in Ably, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Ably to E2b

View example

Reconnect to an E2B sandbox from an Ably request

Use an incoming Ably-related HTTP request to reconnect to an existing E2B sandbox and retrieve its details.

View example

Create an E2B sandbox for an incoming Ably work request

When an HTTP request arrives with a sandbox template and task context, create a new E2B sandbox from that template.

View example

Retrieve E2B logs for an incoming Ably alert

Use an HTTP request associated with an Ably alert to retrieve logs for the specified E2B sandbox.

View example

Pause an E2B sandbox from an incoming stop request

Use a webhook request to pause the running E2B sandbox it identifies while preserving its filesystem and memory state.

View example

Set an E2B sandbox timeout from an incoming request

When a request specifies a new lifetime, set the timeout for the E2B sandbox it identifies.

View example

Review running and paused E2B sandboxes on a schedule

On a recurring schedule, list the team's running and paused E2B sandboxes for a concise review.

View example

Review recent E2B sandbox lifecycle activity

On a recurring schedule, retrieve the latest lifecycle events across the team's E2B sandboxes for an operations review.

View example

Review E2B team resource metrics on a schedule

Retrieve timestamped CPU, memory, and disk metrics across E2B sandboxes on a recurring schedule.

Supported Triggers and Actions

Notis builds workflows that link Ably to E2b. A trigger fires from one place; an action lands in another.

Ably 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

Create Webhook

ActionInstant

Delete Sandbox

Terminate and permanently delete a sandbox; it cannot be resumed.

ActionInstant

Delete Webhook

Unregister a webhook and stop its lifecycle notifications.

ActionInstant

Delete Template

Permanently deletes a template; running or paused sandboxes must not use it.

ActionInstant

Check API Health

Check whether the service is operational.

ActionInstant

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.