Overview
CircleCI launched a feature that enables organizations to harness the functionality of GitHub Apps for triggering builds. This functions even if the organization was originally set up as GitHub OAuth. Customers do not need to migrate to use this feature. This is achieved by granting CircleCI both GitHub App and GitHub OAuth App permissions.
How does this work?
Webhooks serve as a bridge, connecting a platform (like CircleCI, a custom API, or a third-party service) to a continuous stream of future events. Establishing an inbound webhook as a custom trigger on CircleCI allows a third-party service to initiate a CircleCI pipeline. Essentially, any service capable of sending a webhook or executing a curl request can trigger a CircleCI pipeline.
Setting up Custom Webhooks
Use custom webhooks to trigger a pipeline from anywhere that can emit a webhook or run a curl command.
Follow these steps to set up and test a custom webhook trigger. Trigger from anywhere that can emit a webhook or run a curl command:
See our community forum for more details or how to use this functionality with a 3rd party service like DockerHub.