# Send changes to another system with webhooks

> A webhook calls an address of yours whenever records in a table are created, updated or deleted, so another system hears about changes without asking.

Source: https://artavolo.com/page/webhooks

A webhook is Artavolo calling you. When records in a table are created, updated or deleted, Artavolo sends the records to an address you choose, so your own system hears about the change at once instead of asking every few minutes.

## Add a webhook

1. Open the base and press **Settings** at the top right.
2. Choose **Webhooks**, then press **Add new**.
3. Give it a **Title** and pick the table under **Select table**.
4. Under **Which events should trigger this webhook?**, tick **Rows are created**, **Rows are updated**, **Rows are deleted**, or any mix of them.
5. Choose the **Method** (usually POST) and type the **URL** to call.
6. Under **Additional headers**, press **Add header** for anything your endpoint needs, such as a secret or an authorisation header.
7. Press **Save**. The **Status** switch turns a webhook off without deleting it.

![The Webhooks window of a base with no webhooks yet and an Add new button](https://artavolo.com/site/templates/default/assets/img/help/webhooks.webp)

## See what will arrive

While you edit a webhook, **Example payload** shows the exact request for each event, with your headers in it, so you can build the receiving end before you switch it on. A request is JSON with the event type (`rows.created`, `rows.updated` or `rows.deleted`), the table, base and workspace ids, and the records. The `X-Artavolo-Event` header names the event, so one endpoint can handle all three. Tick **Use field name instead id** to get the records keyed by field names rather than internal field ids.

## What sets it off

Changes made on screen or on a phone, through a form, through the API, by AI chat or by an AI agent all set it off. The person who made the change does not wait for your endpoint: the call is made after their change is saved.

## Good to know

- Only the base's owners can add, change and delete webhooks.
- Answer quickly and do the work afterwards. Artavolo waits at most 10 seconds for an answer and does not send a failed call again, so keep your own log if a missed change matters.
- Use HTTPS and check a secret header of your own: anyone who learns the address could post to it. In our cloud a webhook cannot call an address on a private network.
- A white-labelled installation sends the event header under its own name instead of `X-Artavolo-Event`.
- For Zapier, Make, n8n or your own program, a signed subscription through the Airtable-compatible API may suit better: each delivery carries an HMAC signature and only records the subscriber may read. See [Connect Zapier, Make or n8n](https://artavolo.com/page/zapier-make-n8n).
- To call an address only when a condition is met, use an automation with a webhook step instead.

## Related

- [Automations](https://artavolo.com/page/automations)
- [Connect Zapier, Make or n8n](https://artavolo.com/page/zapier-make-n8n)
- [Use the REST API and API tokens](https://artavolo.com/page/rest-api-and-tokens)
