Webhooks
A webhook notifies an outside system when something happens in a Grid.
The description in the interface:
Webhooks are automatic messages sent when something happens. They carry a message or payload and are sent to a unique URL.
Two directions, two places
| Direction | Set up in |
|---|---|
| ApptiveGrid → outside system | Space settings → Webhooks — this page |
| Outside system → ApptiveGrid | Flow trigger Webhook |
Both are called "webhook", but they do opposite things.
Creating a webhook
- Open Space settings → Webhooks.
- Click Create webhook.
- Give it a name under Webhook name. The default is My Webhook.
- Set the event under Trigger the Flow when.
- Enter the target URL and click Save.
Via Edit and Delete, you manage existing webhooks.
Name it descriptively
With several webhooks, "My Webhook" doesn't say anything. Name it after its target and purpose — "Inventory system: new order".
Events
| Event | Trigger | Additional selection |
|---|---|---|
| New entry | An entry is created | Space, Grid |
| Entry changed | An entry is changed | Space, Grid |
| New entry via form | A form creates one | Space, Grid, form |
| Entry changed via form | A form changes one | Space, Grid, form |
Via Select Space, Select Grid, Select event, and Select form, you narrow it down.
Deprecated events
Older webhooks may use events marked deprecated in the dialog. They keep working, but should be replaced when you revise them.
Webhook or Flow?
Both react to the same events. The difference:
| Webhook | Flow | |
|---|---|---|
| Purpose | Pass along raw data | Do something |
| Logic | none | conditions, loops, multiple steps |
| Recipient | one system | any number of actions |
| Requirement | recipient can process JSON | – |
For most cases, a Flow is the right approach
A webhook just forwards data. If you want to filter ("only for amounts over €1000"), enrich, or trigger multiple things, you need a Flow — there, the HTTP request step is the counterpart to a webhook, but with logic in front of it.
A webhook is worth it when a system simply needs to be notified of every change.
Limits
Number per Space depends on your plan
Once the limit is reached, Create more webhooks appears with an upgrade prompt.
No delivery tracking in the interface
Unlike Flow runs, there's no history showing whether a webhook arrived. If delivery fails, you'll only notice it at the target system.
Where traceability matters, a Flow is the better choice — there you can see every run along with any errors.
Security
The target URL receives your data
The webhook sends the content of the entry to the address you entered. Check:
- Is the address correct and current?
- Is it transmitted over HTTPS?
- Is the recipient even allowed to receive this data?
For personal data, this needs a data protection review.
Remove webhooks you no longer need
A webhook keeps firing even if the target system was shut down long ago. Review the list regularly — especially after system changes.