As part of our continued effort to help customers validate change no matter where it comes from, we’re excited to release inbound webhooks to open preview.
CircleCI customers can now trigger a pipeline from any location that can emit a webhook or run a curl request. This means you can validate changes from external tools, existing CircleCI pipelines, changes to a model registry or dataset, or non-commit/ non-PR code repository events, like GitHub comments.
Note: Inbound webhooks are currently only available to customers connecting GitHub to CircleCI via the GitHub App. Additional features and availability will be coming soon.
Check out our how-to guide below and let us know what you think. We’re always looking for feedback so feel free to add comments to this post or email our team directly at email@example.com
Creating a webhook trigger
Go to Project Settings >> Triggers >> Add trigger
Select “Inbound Webhook” and then “Next”
Input your “Trigger Source” name (the tool or website your trigger is originating from) and description (so you can differentiate pipelines later) and click “Save”
Complete set up and get the webhook URL and secret (you will copy this webhook URL into your respective trigger source or tool)
You’ll then need to go to the external source of change from which you are accepting the webhook event (e.g. Datadog, Docker, Hugging Face) and set up the webhook there, like in the example below.
Note: if you set up a webhook in a 3rd party provider using the URL generated in CircleCI, every time that URL is pinged, a pipeline will be triggered using the config.yml in your repo in your main branch.