Dynamic URL Templates
Use `{{ field.path }}` placeholders in endpoint URLs — resolved per-event against the live payload.
Add {{ field.path }} tokens anywhere in the webhook URL. At dispatch time, each token is resolved against the outgoing (post-mapping) payload using dot-notation. If the token is not found in the mapped payload, the original pre-mapping payload is consulted as fallback. Values are rawurlencode()'d before substitution. Free from 3.0.0 — URL templates shipped in Webhook Actions Pro until then.
Example URLs
https://api.hubapi.com/crm/v3/objects/deals/{{ _hs_deal_id }} — injects the deal ID per event. https://api.example.com/users/{{ user.id }}/orders/{{ order.id }} — multiple tokens resolved independently.
Helper keys that never reach the vendor
Since 3.2.0 a top-level payload key that starts with __ is treated as feed-stock for the URL and headers only: it is resolved into the template and then stripped from the body right before the request is sent. Build with AI uses the convention when it writes a dynamic call — https://api.github.com/repos/{{ __repo }}/issues with a Code Glue snippet that sets $payload['__repo'] from post meta — and a template saved through the agent keeps its braces, which an earlier version of the AI write path stripped.
/ Related
