# For Operations Teams (/docs/developer-resources/guides/webhook/for-operations-teams)

Webhooks keep your other systems in step with Monime. When a customer completes a payment, a payout fails or a checkout session expires, Monime sends the details to your systems straight away, so your accounting, CRM or notification tools update without anyone polling or copying data.

You don't need to write code to create or monitor a webhook: the dashboard collects everything through a form. You do need a developer to build the **endpoint**, the address on your server that receives the notifications. This page is for the people who set up and watch webhooks from the dashboard.

## Who does what

| Task                                                           | Usually done by                         |
| -------------------------------------------------------------- | --------------------------------------- |
| Decide which events matter to the business, and who is alerted | Operations                              |
| Build the endpoint, and verify each notification's signature   | Developer                               |
| Create the webhook in the dashboard                            | Either                                  |
| Watch deliveries and respond to alert emails                   | Operations                              |
| Fix failing deliveries                                         | Developer, with details from Operations |

## Before you create a webhook

- **An endpoint URL.** Your developer gives you an HTTPS address that Monime can reach over the internet.
- **Developer access** to your Space. If you don't see Developer in the dashboard's navigation, ask your Space administrator.

## Agree the settings with your developer

Most fields in the create dialog depend on how the endpoint is built. Agree these before you start:

| Setting             | What to agree                                                                                                       |
| ------------------- | ------------------------------------------------------------------------------------------------------------------- |
| URL                 | The endpoint's full HTTPS address                                                                                   |
| Verification method | HMAC-SHA256 (most common) or ECDSA P-256. Hand over the secret, or the public key once the webhook exists, securely |
| API release         | The release the endpoint's code expects                                                                             |
| Events              | Which events the endpoint handles, such as `payment.processing_completed` or `payout.failed`                        |
| Custom headers      | Any header the endpoint needs, such as an `Authorization` token                                                     |
| Alert emails        | Up to two addresses, ideally a team inbox                                                                           |

Then follow [Creating webhooks](/docs/developer-resources/guides/webhook/creating-webhooks), which explains every field.

## Keep an eye on deliveries

Each webhook's details page has an **Event Deliveries** table showing whether each notification reached your systems:

- **Success** means it arrived. Nothing to do.
- **Scheduled** means Monime will try again. A few during your developer's deployments are normal.
- **Failed** means Monime has stopped trying. Tell your developer.

When Monime emails you about failures, open the webhook, filter the table to Failed, and open one of the deliveries. Share its **event name**, **time** and **Last HTTP code** with your developer. Once they've fixed the endpoint, click **Replay** on the failed deliveries so your systems catch up. See [Monitoring and debugging](/docs/developer-resources/guides/webhook/monitoring-and-debugging).

## Routine tasks

| To…                                    | Do this                                                                                   |
| -------------------------------------- | ----------------------------------------------------------------------------------------- |
| Pause notifications during maintenance | Disable the webhook, and enable it afterwards. Events during the pause are not sent later |
| Change who gets alerts                 | Edit the alert emails on the details page                                                 |
| Stop using a webhook                   | Disable it first; delete it once you're sure. Deleting can't be undone                    |

See [Managing webhooks](/docs/developer-resources/guides/webhook/managing-webhooks) for each step.

## Next steps

- [Creating webhooks](/docs/developer-resources/guides/webhook/creating-webhooks)
- [Monitoring and debugging](/docs/developer-resources/guides/webhook/monitoring-and-debugging)
- [FAQ](/docs/developer-resources/guides/webhook/faq)