What's new in v0.15.8
Guided webhook mapping
- Settings > Integrations > Webhooks & API now loads approved Utility templates and renders the variables each selected template needs.
- Operators can map recipient phone numbers, external IDs, body variables, URL button variables, and PDF document header links from payload dot paths, literals, or JSON values.
- A sample-payload dry-run preview shows the resolved transactional template-send request before the webhook config is created.
Safety hardening
- New webhook configs remain disabled and dry-run by default.
- Server routes reject direct live-mode promotion until a future run-log verified promotion flow lands.
- Mapping targets reject unsafe
__proto__,prototype, andconstructorsegments. - Runtime mapping supports prefixed
path:,literal:, andjson:expressions while preserving legacy unprefixed dot paths.
Template support
- Receipt-link and PDF receipt flows are covered, including URL button variables and DOCUMENT header links.
- Named BODY variables now compile to Meta
parameter_nameentries for NAMED templates.