Introduction to automations
Automations let you run actions automatically when something happens in your project. Instead of manually kicking off test suites after every deploy or sending webhook notifications by hand, you define the trigger and actions once and Buildprint handles the rest.
How automations work
Each automation has two parts:
Trigger - the event that starts the automation. This can be a project event like a deploy going live or a branch being merged, a Manual / API run that you queue on demand, or a recurring schedule.
Actions - what happens when the trigger fires. You can run tests, deploy an agent, send a webhook, or any combination of these.
When a trigger fires, Buildprint executes each action in order. If an action fails, the remaining actions still run and the error is recorded. Manual / API automations are queued explicitly through Buildprint's public REST API or MCP tools instead of waiting for a Bubble event.
What you can automate
Run tests on every deploy - trigger your test suite or test groups whenever a new version goes live.
Notify external systems - send a webhook to Slack, Zapier, or your own backend when branches are merged or created.
Deploy an agent - kick off an agent with a prompt that includes context from the trigger, like the branch name, then forward the final result by email, webhook, or Slack.
Run on demand from your tooling - create a Manual / API automation and queue it from MCP or the public REST API when you want a repeatable workflow without waiting for a deploy or branch event.
Scheduled checks - run tests or agents on a recurring schedule (hourly, daily, weekly, or a custom cron expression).
The automations page
Navigate to your project and open the Automations tab in the sidebar. The page shows all active automations in a table with:
Name - the automation name you chose.
Trigger - which event or schedule starts it.
Actions - a summary of what it does (for example, "Run tests, Send webhook").
Created by - which workspace member created the automation.
Enabled - a toggle to turn the automation on or off without deleting it.
Last run - when it last fired and whether it succeeded.
You can disable an automation temporarily without losing its configuration. Toggle it back on whenever you are ready.
How this section is organized
The rest of this collection walks through creating and configuring automations:
Creating automations covers the editor, naming, triggers, and managing automations.
Actions goes through each action type - running tests, deploying agents, and sending webhooks - including branch selection, template parameters, send-result destinations, and payload previews.