---
title: Webhook Event Types
description: Reference of all Capawesome Cloud webhook event types — when each fires for builds, deployments, and jobs.
---

# Event Types

When you create a webhook, you subscribe it to one or more events. Capawesome Cloud then sends a request each time one of those events occurs.

The following events are currently supported:

| Event | Fires when |
| --- | --- |
| `app_build_created` | A new app build is created. |
| `app_deployment_created` | A new deployment is created. |
| `job_created` | A new job is created. |
| `job_finished` | A job finishes (succeeded, failed, or canceled). |

## Resource events vs. job events

It helps to know the difference between the two kinds of events:

- **Resource events** (`app_build_created`, `app_deployment_created`) fire the moment a build or deployment is *created* — useful to know that work has started.
- **Job events** (`job_created`, `job_finished`) track the *execution* behind that work. Every build and deployment runs as a job, so `job_finished` is the event to subscribe to when you care about the outcome — its payload carries the final `status` and links back to the build or deployment via `appBuildId` / `appDeploymentId`.

In practice, most integrations subscribe to `job_finished` to react to a build or deployment succeeding or failing.

The request body for every event follows the same envelope — see [Payload structure](payload-structure.md).

Need an event that's not listed here? [Let us know](../../support/index.md) and we'll look into adding it.