Triggering pipelines

Pipelines in Buddy can be triggered in three different ways:

  1. Manually – on click via Buddy's website
  2. Automatically – on every push to the repository
  3. Recurrently – on a time interval

Apart from that, pipelines can also be triggered using:

  1. Webhooks
  3. Commit commands
  4. Slack commands


If you want to trigger your pipeline with a webhook, go to the given pipeline, click on the burger menu (3 dots) and select the Webhook URL. A box will appear with a URL that can be used to run the pipeline from a remote service: HTTP RequestHTTP Request

By default, every request will trigger an execution to the HEAD revision in the branch. Optionally, you can send some parameters to customize the execution. These parameters can be sent either in a URL query, or as POST parameters.


Run to revision
revision=38ebd0cc80895dadbf0e8c3d667123630f64ec6a (example)

Upload from scratch

Clear cache


Branch (for wildcard pipeline)

Tag (for wildcard pipeline)

Custom ENV VARs


HTTP GET with parameters in query:


HTTP POST with Content-Type: application/json

  "comment": "my comment",
  "clearCache": 1,
  "env1": "env value"

HTTP POST with Content-Type: application/x-www-form-urlencoded



Another way of triggering the pipelines is using Buddy's external REST API. What you need to do is execute the Resource URL (below) and send to it POST Param to_revision.


API requests need to be authorized first. For that, you can either use OAuth or a personal access token.

Commit commands

Pipelines can also be run remotely from the terminal with commands attached to commit messages. For example, $ git commit -am "website hotfix --run production --env key=value" will trigger a pipeline named 'Production'.

Run a specific pipeline--run NAME --run "NAME WITH SPACES"
Do not run (automatic) pipelines--skip
Clear cache before running--clear-cache
Upload everything from scratch--from-scratch
Set variables--env key=value


Integrating Buddy with Slack will let you run pipelines with slash commands. To configure the integration, go to the pipeline details and click Slack handle in the right menu. The option will open a box with the pipeline URL required to configure the slash commands: Slack Slash CommandsSlack Slash Commands

Slash commands

Once configured, you can run the following commands from your Slack channel:

Get pipeline status/[name] status
Run execution/[name] run
Run execution + clear cache/[name] clear run
Cancel execution (must be in progress)/[name] cancel
Run execution again (must be terminated or canceled)/[name] retry
Run execution from scratch/[name] refresh
Run execution from scratch + clear cache/[name] clear refresh
Run and refresh can be used with any revision/[name] run/refresh 1c002dd
Clear and revision can be run together/[name] clear run 1c002dd
Approve a waiting pipeline/[name] approve
Pass params to the waiting pipeline:/[name] params a=b c="some text"*

*[name] is the name of the command that you entered in Slack.

For wildcard pipelines you can send the branch, tag or pull request:

/[name] clear run tag=1.1
/[name] clear run branch=dev
/[name] clear run pullRequest=feature-update
/[name] clear run revision=1c002dd

Last modified on February 16, 2023


Not sure how to configure a pipeline for your process? Reach out on the live-chat or contact support

Get Started

Sign up for free and deploy your project in less than 10 minutes.