Start incident triage with an API health check
A new incident detail can prompt a quick check that E2B's API is reachable.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
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.
Why this helps
Troubleshooting can drift when it's unclear whether a problem comes from the service or one sandbox.
- Add a fast service check to an incident update.
- Help separate broad API availability questions from local debugging.
- Reduce the effort to remember a basic triage step.
Setup
Build it in a few focused steps.
- 1Connect Notion and E2B to Notis once in the portal.
- 2Create an automation that checks E2B API health when the incident page receives a relevant update.
- 3Select Page Content Updated and scope it to the incident page.
- 4Choose a run-report channel and test by updating the page with a real incident detail.
Questions about this workflow
Does an unhealthy result diagnose the issue?
No. It reports API health and can help guide the next investigation step.
Will every page edit run it?
Scope the trigger to the incident page and describe which updates are relevant.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to E2b. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
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.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Connect any two apps with Notis in the middle.
Notion 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.