Skip to content
Nappai Documentation

Runloop Sandbox

The Runloop Sandbox acts as a secure, isolated workspace within the Nappai automation system. It is designed to safely manage repetitive tasks, iterative processes, and autonomous agents. Think of it as a dedicated engine or testing ground where your automation logic runs without interfering with the rest of your workflow, ensuring stability and reliability.

How it Works

This component serves as a container for your automation tasks. When activated, it sets up a protected environment to handle processes that may run in loops or involve smart agents. While the sandbox manages the security and structure of the execution, the actual logic for running your processes is handled by the underlying system connected via the Runloop API. It ensures that your workflows remain predictable and that resources are managed efficiently.

Connection & Credentials

This component requires configuring a credential in the Nappai panel before interacting with the external service:

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type Runloop API and fill in the required field: Runloop API Key. You can obtain your API key from the Runloop Platform.
  3. In your workflow, select the saved credential in the Credential input field of this node.

Inputs

Input Fields

This component does not require manual input fields. All necessary configuration is managed through the Credential selection described above. The component automatically handles the setup required to connect to the Runloop environment and execute processes.

Outputs

Upon completion, the Runloop Sandbox provides a structured result containing the status of the execution, any data produced by the process, and helpful metadata. You can use this output to make decisions in subsequent steps, such as logging the result or triggering further actions based on the outcome.

Output Data Example (JSON)json

{ “status”: “success”, “output”: “Automated process completed.”, “metadata”: { “elapsed_time”: 2.5, “iteration_count”: 4, “agent_state”: “idle” }, “logs”: [ “Process initiated.”, “Iteration 1 completed.”, “Iteration 2 completed.”, “Finalization complete.” ] }

Connectivity

This component typically connects to automation triggers or other action nodes to initiate workflows. After execution, its output can be linked to nodes that require processing results, logging data, or performing conditional branching. For example, you might connect the sandbox to a notification node to alert you when a long-running agent process finishes.

Usage Example

Imagine you are building a workflow to monitor a database for new records automatically. You add the Runloop Sandbox to your workflow and select your Runloop API credential. When the workflow is triggered, the sandbox manages the iterative process of checking for new records. It ensures the checks run safely and repeatedly until the task is complete, then returns a final status and any data collected, allowing you to pass this information to the next step in your automation.

Tips and Best Practices

  • Ensure your Runloop API Key has the necessary permissions to run the desired processes.
  • Check the iteration_count in the output to understand how many times your process ran, which helps in debugging performance.
  • Use the sandbox for complex or repetitive tasks to keep your main workflow clean and manageable.
  • Always select a valid credential to avoid connection errors during execution.

Security Considerations

  • Always keep your Runloop API Key secure and do not share it publicly.
  • The sandbox provides an isolated environment to help protect your data, but ensure your API credentials are managed carefully within Nappai.
  • Rotate your API keys regularly through the Runloop Platform to maintain security best practices.