inbound-webhook-to-records

Use it when

• A system sends an HTTP call for each event: a form, a payment, a shipment update.
• Up to a few hundred calls per hour; each call starts one run.
• Each call's body is under 20 MB, the size the webhook accepts.

Above a few hundred per hour or into a rate limited app, add a queue (see Variations).

Why this design

Advantages:

• The sender pushes the event the moment it happens; no polling delay.
• The run receives body, headers and query_parameters, so one workflow can check a signature header and route by event type.