Skip to main content

Dynamic Flows

Endpoint

Any Flow that is of dynamic type must have an endpoint configured during its creation so it can perform exchanges of data between screens. In addition to data exchange, the endpoint is also responsible for managing which will be the next screen of the flow.
The endpoint must always be active and responding. If the endpoint experiences issues, the Flow may suffer throttling by WhatsApp. Learn more in the section on Endpoint Health / Throttle.

Webhook

The webhook of the number that sent the Flow will be called only after the Flow is filled out and sent by the user on a screen that has the terminal: true property. Example of webhook to be filled in after sending by the user:
This webhook belongs to one of our Flows examples. You can access the example Flow this webhook belongs to at Flow Samples.

Endpoint Health / Throttle

Flows with unstable endpoints may be throttled by WhatsApp. When the endpoint experiences failures or slow responses, WhatsApp may limit the number of allowed requests, affecting the Flow’s availability to users. Monitor your endpoint health regularly to avoid these throttles.