--- title: "Trigger options" description: "Explore the ways to trigger pipelines in CircleCI, from repository events and custom webhooks to the web app, the API, and schedules." platform: "Cloud, Server" doc_version: "Server" last_updated: "2026-10-26" --- > For current CircleCI product defaults, deprecated patterns, and Cloud/Server differences, see [AGENTS.md](https://circleci.com/docs/AGENTS.md). > > For the complete documentation index and site structure, see [llms.txt](https://circleci.com/docs/llms.txt). # Trigger options Pipelines are triggered in response to actions or scheduled to run at specific times and frequencies. Each method of triggering a pipeline is described below. ## Trigger a pipeline on a repo event Trigger a pipeline on an event in your repository. The options available to you will be different depending on which integration you have set up, and for GitHub accounts, which GitHub authentication method you use. Once triggered, a running pipeline appears on the pipelines dashboard, which is accessible by selecting **Pipelines** from the left hand sidebar in the CircleCI web app. This option is called **Dashboard** if you are using CircleCI Server. > **Image:** Screenshot showing running pipelines in the CircleCI dashboard. Figure 1. Pipeline running and visible on the dashboard ## Trigger a pipeline from the CircleCI web app 1. In the [CircleCI web app](https://app.circleci.com/home), select your organization from your homepage. 2. Select **Pipelines** for your project. If you do not see your project listed, select **Projects** in the sidebar to get to a full list. You will now be on your project’s pipelines page. 3. Select **Trigger Pipeline**. > **Image:** Screenshot showing location on trigger pipeline button in the CircleCI web app Figure 2. Screenshot showing the trigger pipeline button in the CircleCI web app 4. Select the pipeline you want to trigger from the dropdown menu. 5. Select your config source branch. This tells CircleCI where (repo and branch) to find your pipeline config. > **Image:** Trigger a pipeline modal in the CircleCI web app Figure 3. Screenshot showing the trigger pipeline modal 6. If your code is integrated via the **GitHub App or Cursor Origin**, select your checkout source and branch. This tells CircleCI which code to check out when running a [`checkout` step](https://circleci.com/docs/reference/configuration-reference/#checkout). If your code is integrated via **GitHub OAuth or Bitbucket Cloud**, you can skip this step, the same location is used for both config and checkout source. 7. If you would like to specify any pipeline parameters, select **Add +** and enter the required fields. 8. Select **Run Pipeline** and you will see your new pipeline running in the web app. If your GitHub user account connection to CircleCI is not yet authorized, you will need to select **Authorize** in the trigger pipeline modal to connect and continue. ## Trigger a pipeline using the API **Using server?** If you are using CircleCI Server, replace `[https://circleci.com](https://circleci.com)` with your server hostname when interacting with the CircleCI API. This method is supported for GitHub (OAuth and App), Bitbucket (Cloud and Data Center), and Cursor Origin orgs. **GitHub OAuth and Bitbucket Cloud pipelines** can also be triggered using the [Trigger a New Pipeline](https://circleci.com/docs/api/v2/index.html#operation/triggerPipeline) endpoint, which is described in the **CircleCI Server** tab. However, the method outlined in this section is recommended. Trigger a pipeline for a project using the [v2 API endpoint](https://circleci.com/docs/api/v2/index.html#tag/Pipeline/operation/triggerPipelineRun) `https://circleci.com/api/v2/project//pipeline/run`. 1. If you have not already, get set up to use API v2 by following the steps in the [API Developers Guide](https://circleci.com/docs/guides/server/toolkit/api-developers-guide/#authentication-and-authorization). 2. In the [CircleCI web app](https://app.circleci.com/home/) select your organization. Over the next few steps you will collect the data you need to trigger your pipeline. 3. Find your project slug: 1. Select **Projects** in the CircleCI web app sidebar. 2. Find your project. 3. Select the ellipsis menu and choose **Project Settings**. 4. Copy your project slug. Save this somewhere, you will need it later. 4. Find your definition ID: 1. You are in project settings if you are following these steps in sequence. If not see previous steps to get there. Select **Project Setup** in the sidebar, or **Pipelines** if you are using Bitbucket Cloud. 2. Copy the definition ID for the correct pipeline. Save this somewhere, you will need it in the next step. > **Image:** screenshot showing location of pipeline definition ID copy button Figure 4. Screenshot showing the pipeline definition ID copy button 5. To trigger a pipeline from the command line using `curl`, copy and paste this sample request and replace the details in `< >` with your details. The key `parameters` is optional: ```shell curl -X POST https://circleci.com/api/v2/project//pipeline/run \ --header "Circle-Token: $CIRCLE_TOKEN" \ --header "content-type: application/json" \ --data '{ "definition_id": "", "config": {"branch": ""}, "checkout": {"branch": ""}, "parameters": {"": ""} }' ``` 6. To run a pipeline based on a **tag** instead of a **branch**, replace the `config` and/or `checkout` fields with: ```shell "config": {"tag": ""}, "checkout": {"tag": ""} ``` 7. Head back to the CircleCI web app and see your pipeline running on the dashboard. 1. If you have not already, get set up to use API v2 by following the steps in the [API Developers Guide](https://circleci.com/docs/guides/server/toolkit/api-developers-guide/#authentication-and-authorization). 2. To trigger a pipeline from the command line using `curl`, copy and paste this sample request and replace the details in `< >` with your details, VCS can be `gh` or `bb`: If you are using CircleCI Cloud, `` is `circleci.com`. ```shell curl -X POST https:///api/v2/project////pipeline \ --header "Circle-Token: $CIRCLE_TOKEN" \ --header "content-type: application/json" \ --data '{"branch":""}' ``` 3. Head back to the CircleCI web app and see your pipeline running on the dashboard. You can also specify pipeline parameters when triggering a pipeline using the API. For full details, see the [API v2 Docs](https://circleci.com/docs/api/v2/index.html#operation/triggerPipeline). ## Schedule a pipeline To run a workflow on a schedule, use a scheduled workflow. Add a `triggers` key with a `cron` schedule to the workflow in your `.circleci/config.yml` file. See [Scheduling a Workflow](https://circleci.com/docs/guides/server/orchestrate/workflows/#scheduling-a-workflow). ## GitHub webhook settings It is possible to edit the webhooks in GitHub to restrict events that trigger a build. Editing the webhook settings lets you change which hooks get sent to CircleCI, but does not change the types of hooks that trigger builds. CircleCI will always build push hooks, and build on PR hooks (depending on settings), but if you remove push hooks from the webhook settings, CircleCI will not build. Refer to the [GitHub Edit a Hook document](https://developer.github.com/v3/repos/hooks/#edit-a-hook) for details. ## Next steps Read about orchestrating elements of work within pipelines on the [Using Workflows to Orchestrate Jobs](https://circleci.com/docs/guides/server/orchestrate/workflows/) page.