- Home
- Connectivity
- Webhooks
Webhooks
Bitrise makes extensive use of incoming webhooks to automatically trigger builds on Bitrise and outgoing webhooks to send reports of build events to other services, such as Slack.
A webhook is a user-defined callback that is triggered by some event, such as pushing code to a repository. Bitrise makes extensive use of webhooks:
-
Incoming webhooks, registered with your Git service provider, are used to automatically trigger builds on Bitrise.
Webhook issues
If your builds triggers don't work, there might be a problem with your webhooks: Builds aren't getting triggered.
-
Outgoing webhooks are used to send reports of build events to other services, such as Slack.
You can add an incoming webhook automatically either when creating an app or later; it’s also possible to manually add a webhook to any supported service.
Outgoing webhooks can be added either on the website or via the Bitrise API.
An app on Bitrise represents a Git repository that stores source code and has been connected to Bitrise to be able to run builds on it. As such, a Bitrise app isn't necessarily an actual application: it's just the code on which you run builds with Bitrise.
An app on Bitrise represents a Git repository that stores source code and has been connected to Bitrise to be able to run builds on it. As such, a Bitrise app isn't necessarily an actual application: it's just the code on which you run builds with Bitrise.