Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Daytona
WordPress

Connect Daytona and WordPress

Explore ready-made Daytona and WordPress templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Daytona with WordPress and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

WordPress
Trigger: Watch Categories
Daytona
Action: Select an action
1. Select a trigger

  • Triggers when a new category is added.

  • Triggers when a new comment is added.

  • Triggers when a new media item is added.

  • Triggers when a new post is added.

  • Watches for updated posts.

  • Triggers when a new tag is added.

  • Triggers when a new user is added.

2. Select an action

  • Creates a Daytona sandbox using the documented CreateSandbox schema.

  • Creates a Daytona snapshot from an image using the documented CreateSnapshot schema.

  • Creates a directory inside a sandbox (Daytona toolbox).

  • Delete a Sandbox by ID or name.

  • Deletes a file or directory inside a sandbox (Daytona toolbox).

  • Downloads a file from a sandbox as binary data (Daytona toolbox).

  • Executes a command synchronously in a sandbox via the Daytona toolbox proxy (resolved per sandbox from /sandbox/{id}/toolbox-proxy-url).

  • Gets a Daytona sandbox port preview URL.

  • Gets Daytona sandbox details by ID or name.

  • Gets metadata for a single file or directory inside a sandbox (Daytona toolbox).

  • Stages files in a Git repository inside a sandbox (Daytona toolbox).

  • Checks out a branch or commit in a sandbox Git repository (Daytona toolbox).

  • Clones a Git repository into a sandbox (Daytona toolbox).

  • Commits staged changes in a Git repository inside a sandbox (Daytona toolbox).

  • Pulls changes from the remote into a sandbox Git repository (Daytona toolbox).

  • Pushes commits from a sandbox Git repository to its remote (Daytona toolbox).

  • Gets the Git status of a repository inside a sandbox (Daytona toolbox).

  • Performs an arbitrary authorized API call.

  • Moves or renames a file or directory inside a sandbox (Daytona toolbox).

  • Start a Sandbox by ID or name.

  • Stop a Sandbox by ID or name.

  • Uploads a file into a sandbox at the given path (Daytona toolbox, multipart upload).

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Daytona and WordPress.

Create a Category
Creates a category.
Action
Create a Comment
Creates a comment.
Action
Create a Media Item
Creates a media item.
Action
Create a Post
Creates a post.
Action
Create a sandbox
Creates a Daytona sandbox using the documented CreateSandbox schema.
Action
Create a snapshot
Creates a Daytona snapshot from an image using the documented CreateSnapshot schema.
Action
Create a Tag
Creates a tag.
Action
Create a User
Creates a user.
Action
Create folder
Creates a directory inside a sandbox (Daytona toolbox).
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.