Pause a Sandbox for Later
Suspend idle work without losing the environment you already prepared.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Pause Sandbox
Tool to pause a running E2B sandbox preserving its filesystem and memory state. Use when you need to temporarily suspend a sandbox while maintaining its state for later resumption. Takes approximately 4 seconds per 1 GiB of RAM to pause. Paused sandboxes can be stored for up to 30 days.
Why this helps
Keeping idle sandboxes running wastes resources, while stopping them loses context.
- Preserves filesystem and memory
- Reduces active resource use
- Supports clean work handoffs
Setup
Build it in a few focused steps.
- 1Connect 0CodeKit and E2b in Notis once.
- 2Create an automation named Pause sandbox for later.
- 3Tell Notis to pause the supplied sandbox when work is marked temporarily idle.
- 4Choose the webhook trigger and report destination.
- 5Test it with a noncritical sandbox.
Questions about this workflow
Can the sandbox be resumed later?
Yes. Reconnect to the paused sandbox when you are ready to continue.
How long does pausing take?
Pausing takes approximately four seconds per GiB of RAM.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 0CodeKit to E2b. A trigger fires from one place; an action lands in another.
0CodeKit 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.
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.
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.
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.
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.
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.
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.
0CodeKit 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.