Webhooks, retries, and idempotency: design for repeated delivery
Keep event receipt, durable processing, duplicate detection, and business effects separate in a recoverable webhook workflow.
Topic reading list / 2 articles
Process Automation.Recurring work, deliberate behavior.
Follow the path from a business trigger to a recoverable outcome. The related guides discuss state, event identity, side effects, and the points where a workflow should wait for a person. Read the automation overview before the webhook deep dive when designing a new event-driven process. Use both to identify what must survive a restart and which effects must not repeat.
Reliable process automation: design the trigger, state, and recovery path
A practical method for automating recurring work without turning temporary failures into duplicate actions.
Make the next step a clear one
Build the process.
Not the guesswork.
Start with a map, explore the reference patterns, or open a playbook for the work in front of you.
Open the reference docs