Creating automations
To create an automation, open your project's Automations tab and click Create automation. Buildprint opens the automation editor, which walks you through the three parts: name, trigger, and actions.
Name
Give the automation a descriptive name so you can identify it in the list. Good names describe what happens and why, for example "Run smoke tests on deploy" or "Notify Slack on branch merge".
Choosing a trigger
Select when the automation should fire. Buildprint supports six trigger types:
Manual / API - runs only when you queue it on demand through Buildprint's public REST API, MCP server, or manually through the UI.
Live deployed - fires whenever a new version of your app is deployed to live.
Branch merged - fires when a branch is merged. Includes the source and target branch as parameters.
Branch created - fires when a new branch is created. Includes the new branch as a parameter.
Branch removed - fires when a branch is deleted. Includes the removed branch as a parameter.
Recurring - fires on a schedule. Choose a preset (every hour, every day at 9am UTC, every Monday, every Sunday) or enter a custom cron expression.
Branch-based triggers expose parameters like the branch name and ID that you can use in your actions. Manual / API, Live deployed, and Recurring triggers do not expose branch parameters. See the Actions article for details on template parameters.
Custom cron expressions
If the presets don't fit your needs, select Custom from the schedule dropdown and enter a standard cron expression (five fields: minute, hour, day-of-month, month, day-of-week). You can also type a description like "every weekday at 3pm" and Buildprint will generate the expression for you.
Adding actions
Each automation needs at least one action. Click Add action to add more. Actions run in the order they appear. You can choose from three action types:
Run tests - run individual tests or test groups against a specific branch.
Deploy agent - run an AI agent with a prompt you define and forward the final response by email, webhook, or Slack.
Send webhook - POST a JSON payload to an external URL.
Each action type has its own configuration options, covered in the Actions article.
Editing an automation
Click the menu icon on any automation in the list and select Edit to reopen the editor with the current configuration. Changes take effect immediately after saving.
Enabling and disabling
Use the toggle in the automation list to enable or disable an automation. Disabled automations keep their configuration but won't fire. For recurring automations, disabling cancels the next scheduled run and enabling reschedules it.
Deleting an automation
To permanently remove an automation from the list, click the menu icon and select Delete. Buildprint archives it behind the scenes, hides it from the list, and stops future runs. This cannot be undone.