Webhooks

A webhook trigger gives a workflow a URL. A service that sends an event to that URL starts a run, with the event’s payload available to the workflow.

Creating one

Open Webhooks, create a trigger, and choose:

• the workflow it starts;
• the provider whose events it accepts;
• how to set it up — paste the URL into the service yourself, or have Hegu AI register the subscription with the service;
• the signing secret the service uses, so an event that did not come from it is refused.

Copy the trigger’s URL into the service if you chose to set it up yourself.

What the event becomes

The payload is offered to the workflow as its input. It takes precedence over the input stored on the trigger, so a payload never loses a field to saved configuration. Name a field from the event with a reference, the same way you would name any other input.

Delivery limits

A webhook accepts up to 60 deliveries per minute, counted per trigger and per account, whichever comes first. Beyond that the delivery is refused and the sender can retry it.