All integrations
Daytona logo

Daytona

Cloud ComputingAI Agents

Run code safely in Daytona sandboxes from a workflow: spin up an isolated computer in seconds, run Python, JavaScript, TypeScript or any command in it, move files in and out, clone a repository, share a preview link to an app running inside, and stop, archive or delete it when the job is done.

15 actions

Actions

Steps your workflow can run in Daytona.

Create a sandboxCreate a sandbox and wait until it is running, ready for code, commands and files. By default it stops after 15 idle minutes and keeps its files until you delete it.
List sandboxesThe sandboxes in your organization, newest first, optionally only those in some states, with some labels or whose name starts a certain way. Deleted sandboxes are not listed.
Get a sandboxOne sandbox: whether it is running, its resources, labels and when it stops or deletes itself.
Start a sandboxStart a stopped or archived sandbox and wait until it is running. A running sandbox is left as it is.
Stop a sandboxStop a sandbox and wait until it has stopped. Its files are kept, unless it is set to delete when it stops. A stopped sandbox is left as it is.
Archive a sandboxMove a sandbox's files to cheaper storage, stopping it first if it is running. Starting it later brings everything back. A large sandbox may still say 'archiving' when the step ends; Daytona finishes on its own.
Delete a sandboxDelete a sandbox and everything in it. This can't be undone. If it is starting or stopping, the step waits for that to finish.
Update a sandboxChange when a sandbox stops or deletes itself, or its labels. Only the settings you fill in change.
Get a preview linkA link anyone can open to see an app or site running in a sandbox, such as a web server started with 'Run a command'. The sandbox must be running for the page to load.
Run codeRun Python, JavaScript or TypeScript in a sandbox and get what it printed. Code that fails still returns its output, with 'succeeded' false, so a later step can act on it.
Run a commandRun a shell command in a sandbox, such as installing a package or running tests, and get its output. A command that fails still returns its output, with 'succeeded' false.
Upload a filePut a file in a sandbox: upload one, use a file from an earlier step, or type its text. Folders are created as needed and a file already there is replaced.
Download a fileGet a file out of a sandbox, such as a report or chart your code made, as a file later steps can send or store. A text file up to 1 MB also comes back as 'text'.
List filesThe files and folders in one folder of a sandbox, folders first.
Clone a Git repositoryCopy a Git repository into a sandbox, from GitHub, GitLab or any Git host, so later steps can build, test or read it.

Connect in a few clicks

Authenticate once and every action and trigger for the app is ready to drop into a workflow. No glue code, no maintenance.

Automate across your stack

Chain apps together with triggers, actions, and logic that move data between your tools automatically, so work happens without you.

Secure by default

Credentials are encrypted and scoped per workspace. Connect the tools your team already trusts with confidence.

Automate Daytona with Lodol.

Connect Daytona and build your first workflow in minutes. No credit card required.

Free plan available · No credit card required