# Automate with events
URL: https://docs.awellhealth.com/docs/automate-with-events

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



Webhooks run in both directions here:

* **Outbound webhook**: Awell reports that something happened. A form was submitted or a care flow
  completed, so Awell posts an event to an endpoint the receiving system owns.
* **Incoming webhook**: another system asks Awell to do something. A booking is confirmed elsewhere,
  so that system posts to an Awell URL and a care flow starts.

The direction is easy to get the wrong way around, so every page here says which one it covers.

## Read these in order [#read-these-in-order]

1. [Webhooks and events](/docs/automate-with-events/webhooks-and-events)
   What they are, both directions, and what a payload contains.
2. [Receive webhook events](/docs/automate-with-events/receive-webhook-events)
   Build and secure an endpoint, then take it live. (For engineers.)
3. [Configure webhooks in Studio](/docs/automate-with-events/configure-webhooks-in-studio)
   Turn them on, get the signing secret, and monitor what was sent. (No code.)
4. [Start a care flow from an incoming webhook](/docs/automate-with-events/start-a-care-flow-from-an-incoming-webhook)
   The other direction: something outside Awell begins care.
5. [Webhook event catalog](/docs/automate-with-events/webhook-event-catalog)
   Every event available to subscribe to.