Use webhooks for event-driven connections
Send events to your system or start a Flow from an external event.
Open this guide in the help center →
When to use this. A document completion or form submission should notify your backend.
What you’ll need. An HTTPS receiver or an inbound Flow trigger and a sample event.
Choose the direction
Use an outbound form or document webhook to notify another system. Use an inbound Flow webhook when an external system should start a Formbot automation.
Configure the destination or trigger
Enter the intended endpoint using the relevant app’s settings. For document webhooks, choose the lifecycle events you need and review any document exclusions.
Test with sample data
Trigger one event and inspect what the receiver receives. Use the actual delivered payload to determine field mapping instead of assuming a schema.
Review delivery behavior
Document webhooks provide delivery logs and signed events. Check status codes and failures. Confirm retry and duplicate handling in your receiver before production use.
How to know it worked
The receiver recognizes the event and performs the intended action once.
Features covered
- Form submission webhooks
- Document lifecycle events
- Delivery logs
- Inbound Flow triggers