Automate

Projects and environments

A project is a standing automation with one or more workflows. Each production, staging, or dev environment is an isolated project instance with its own deployment state, workflow runs, triggers, and variable bindings.

Last reviewed July 14, 2026

In the app Automate → Projects

Problems this solves

Start with the recurring problem, then use this feature when its boundary matches the outcome you need.

Problem

Keep an automation running without your laptop

A useful script only runs when its author remembers to start it, and stops when that machine is offline.

How this helps

Deploy it as a Project so its workflows, triggers, configuration, and run history live in a managed environment.

See the calendar-sync project →

Problem

Test changes without touching production

A configuration or workflow change needs realistic testing, but pointing development code at live systems is too risky.

How this helps

Use separate dev, staging, and production project environments, each with isolated deployments, triggers, and variable bindings.

Create a project

Open Automate → Projects and select New project.
Choose a durable name. The CLI uses the resulting project slug when it deploys and runs workflows.
Start with production unless you deliberately need an isolated test environment.
Open the new project. It begins in draft state until workflow source is deployed.

The Projects page groups environments with the same project name into one row. Select the production, staging, or dev chip to work in that specific environment. Creating staging or dev requires a plan with multiple environments enabled.

Deploy source with the CLI

The app can create an empty project, but the CLI uploads the source directory and solidactions.yamlthat define its workflows. From the project directory:

solidactions project deploy my-project -e production

On the first deploy, choose the environment explicitly. To create a missing staging or dev environment while deploying, add --create:

solidactions project deploy my-project -e staging --create

If the source lives elsewhere, pass its path after the project name. The CLI always excludes .envfiles, node_modules, and Git metadata. Keep secrets in Variables, not in the deployment bundle.

First deploy and Rebuild are different actions.

Project → Build → Rebuild queues another build from the source already stored by SolidActions. It does not upload a local directory. Use project deploy whenever the source or YAML changed.

Use the project tabs

Workflows: See deployed workflows, health, recent failures, trigger type, and whether each workflow is enabled.
Runs: Inspect executions for this project environment.
Build: See deployment state and the most recent build log, or queue a rebuild of stored source.
Schedules: Add, pause, reset, or remove cron schedules for the environment's workflows.
Webhooks: Enable webhook endpoints and manage their authentication and response behavior.
Variables: Bind workflow variable names to workspace variables, workflow Connections, or local values.
Settings: Rename the project family, choose its default environment, control the runtime and enabled state, configure failure email alerts, or delete it.

Switch or add an environment

Use the environment picker beside the project name. Existing environments appear with their deployment state; missing environments have an add action. A newly created environment shares the project family name, but it does not share run history or local project values. Workspace Variables resolve the value for the selected environment according to their inheritance settings.

Disable or delete safely

Turning Enabled off in Project → Settings prevents the project's workflows from running. Deleting a project is broader: the confirmation removes the project family and its environments, workflows, runs, and schedules. Use disable when you may need the automation again; delete only after preserving anything you need.

Try a small project

Follow Build workflows for the generated first project, or inspect thehello-world examplebefore adding your own integrations.

Next: configure variables and secrets, choose atrigger, or inspect runs.