Skip to main content

Migrating from pipeline.trigger_source to pipeline.trigger.type

pipeline.trigger_source is being deprecated, and users should now switch to pipeline.trigger.type

Overview

The pipeline.trigger_source pipeline parameter will be deprecated on 21st September 2026, this is in conjunction with the deprecation of pipeline parameters beginning with pipeline.trigger_parameters.* as outlined here. pipeline.trigger.type is the suitable replacement for this value in your CircleCI configuration.

The values are not a one-to-one rename. In particular, webhook under pipeline.trigger_source covered VCS push events. Under pipeline.trigger.type, webhook means a custom webhook only. VCS triggers use provider-specific values, such as github_oauth or bitbucket_cloud.

For the full list of pipeline values, see Pipeline values.

Value mapping

To change to the new pipeline value you may need to update your configuration using the mapping table below

pipeline.trigger_source

pipeline.trigger.type

When to use

webhook (GitHub OAuth project)

github_oauth

Pipeline triggered by a GitHub OAuth VCS event (for example, push)

webhook (Bitbucket Cloud project)

bitbucket_cloud

Pipeline triggered by a Bitbucket Cloud VCS event

webhook (custom webhook)

webhook

Pipeline triggered by a custom webhook

scheduled_pipeline

schedule

Pipeline triggered by a schedule trigger

schedule

schedule

Pipeline triggered by a schedule workflow

api

api

Pipeline triggered by the API or the Trigger Pipeline button in the web app

Additional values available on pipeline.trigger.type that have no direct equivalent in pipeline.trigger_source:

pipeline.trigger.type

Meaning

github_app

GitHub App integration

github_server

GitHub App Server (GitHub Enterprise Server)

bitbucket_dc

Bitbucket Data Center

Additional Resources

Did this answer your question?