Other use cases

Running Bitbucket Pipelines in Slack

Turn Bitbucket pipelines into ready-to-use actions and trigger them in Slack whenever you need to run a pipeline manually.

How it works

Integrating Bitbucket and Slack seamlessly, Actioner brings Bitbucket Pipelines as ready-to-use actions in Slack, without any extra configuration. 

Just by selecting your repository and pipeline, your Bitbucket pipeline action becomes ready to be manually triggered in Slack. Actioner automatically generates this action with the parameters in your pipeline’s YAML file.

Unlike other apps, Actioner does not require complex configurations. You only need to complete a few simple steps to get started!

How to get started

To begin using the app in Slack,

  1. Sign up to Actioner.
  2. Install Bitbucket pipelines app.
  3. Connect to Bitbucket and Slack.
  4. Run the setup action named Create action for a pipeline. Select your Bitbucket workspace, repository, default branch name, the pipelines YAML and your pipeline. 

Running this action automatically adds a new action to the app you installed to your Actioner workspace. The newly created action is automatically generated with the parameters of your selected pipeline.

After running this step during the setup, your pipeline will become ready to be run in Slack, whenever you need to manually trigger it.

💡If you want to convert more pipelines into ready-to-use actions in Slack, re-run the Create action for a pipeline step during the setup by selecting your workspace, repository, default branch name, the pipelines YAML and your pipeline. 

If you are looking to generate additional pipelines available to be triggered in Slack after the setup, follow the below steps:

  1. Call Actioner app in Slack.
  2. Start typing Create action for a pipeline.
  3. Run this action by selecting your Bitbucket workspace, repository, default branch name, the pipelines YAML and your pipeline.

To trigger your pipeline manually in Slack, simply call Actioner app and type the name of your pipeline. Actioner will automatically suggest the action that will trigger your pipeline.

On the opening screen, enter the parameters to run your action. These parameters are the ones you provide to run the same pipeline manually in Bitbucket. They are dynamically generated from the YAML file of your pipeline. You can run your action in Slack-with the same parameters you trigger the selected pipeline manually.

If you completed all the steps during the setup, you’ll get a direct message from Actioner whenever you run a pipeline. More than that, Actioner will notify your team of pipeline results in your preferred Slack channel. Visit Bitbucket pipelines notifications in Slack page to learn how to get notified of your pipeline runs in Slack.

How to get started as an app user

If you are invited to use this app with your colleagues, you only need to connect your Bitbucket account by granting access to Actioner.

To trigger your pipeline manually in Slack, simply call Actioner app and type the name of your pipeline. Actioner will automatically suggest the action that will trigger your pipeline.

On the opening screen, enter the parameters to run your action. These parameters are the ones you provide to run the same pipeline manually in Bitbucket. They are dynamically generated from the YAML file of your pipeline. You can run your action in Slack-with the same parameters you trigger the selected pipeline manually.

If you are looking to trigger a pipeline in Slack, but could not find the action to run it, follow below steps:

  1. Call Actioner app in Slack.
  2. Start typing Create action for a pipeline.
  3. Run this action by selecting your Bitbucket workspace, repository, default branch name, the pipelines YAML and your pipeline.

Frequently asked questions

How can I generate different actions to manually run Bitbucket pipelines?

If you are looking to generate additional pipelines available to be triggered in Slack after the setup, or if you are invited to this app as user, follow the below steps:

  1. Call Actioner app in Slack.
  2. Start typing Create action for a pipeline.
  3. Run this action by selecting your Bitbucket workspace, repository, default branch name, the pipelines YAML and your pipeline.
How can I run a Bitbucket pipeline manually in Slack?

To trigger your pipeline manually in Slack, simply call Actioner app and type the name of your pipeline. Actioner will automatically suggest the action that will trigger your pipeline.

On the opening screen, enter the parameters to run your action. These parameters are the ones you provide to run the same pipeline manually in Bitbucket. They are dynamically generated from the YAML file of your pipeline. You can run your action in Slack-with the same parameters you trigger the selected pipeline manually.

How can I get notified for different Bitbucket pipeline runs in different Slack channels?

If you are looking to generate additional pipeline notifications in different Slack channel after the setup, follow the below steps:

  1. Call Actioner app in Slack.
  2. Start typing Select channel for pipeline run results.
  3. Run this action by selecting your Bitbucket workspace, repository, Slack channels and the events you want to get notified of. Available event types are build in-progress, build succeed and build failed. This action subscribes to the selected events in the selected repo and sends notifications to selected Slack channels for these events.

💡If you want to get notifications for different events in different channels, you can re-run this action.

I'm not getting a direct message when I run a pipeline in Slack

If you don’t receive DM for the pipelines that you have run, please follow the steps described in this documentation.