On top of the default action roster, users can define their own actions in YAML and use them in their pipelines. The actions are run in Docker containers launched from images pulled from the Docker Hub registry. A Docker container acts like a local dev environment with preinstalled operating system, tools, and dependencies. In the container, you can run commands on your repository files, run calls to any publicly available third-party API, and export input data to variables to use them in other actions in the pipeline.
Action definition
Learn how to define your own custom actions using YAML
YAML Configuration
Custom actions are defined as code in a similar manner to default Buddy actions.
Custom tabs
If your custom action has inputs defined, they are displayed in the Setup tab of the action.
Parsing & Versioning
Actions should be created and updated in the default branch of the repository and versioned with Git tags.
Deleting & renaming
Deleting and renaming custom actions.
Custom actions in YAML
Learn how to add custom actions to your pipelines' YAML
YAML parameters
List of all the paramteres used by custom actions
Input Examples
Learn how to use YAML input types in Buddy custom actions to automate AI & SEO workflows in 2025. Includes TEXT, SELECT, PASSWORD & more.