# Trigger Build Actions

The `trigger_build` is an extremely powerful action that will trigger your repository's build. You can control what workflow is executed by specifying the parameters. Your [CI/CD integration](/sleuth-dora/integrations-1/builds.md) defines the required parameters for Sleuth to trigger the build process.

The `trigger_build` action is best used in concert with Sleuth's [Slack based Approvals](/sleuth-dora/slack-mission-control/approvals.md). Together they can be used to define your deployment workflow.

| Integration                                                                                                  |
| ------------------------------------------------------------------------------------------------------------ |
| ​[Bitbucket Pipelines](/sleuth-dora/sleuth-automations/actions/trigger_build/trigger-build-bb-pipelines.md)​ |
| ​[CircleCI](/sleuth-dora/sleuth-automations/actions/trigger_build/trigger-build-circleci.md)​                |
| ​[Github Actions](/sleuth-dora/sleuth-automations/actions/trigger_build/trigger-build-gh-actions.md)​        |
| [Jenkins](/sleuth-dora/sleuth-automations/actions/trigger_build/jenkins.md)                                  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/sleuth-automations/actions/trigger_build.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.