Test webhook data with a dry run
Paste a sample payload into the Dry-Run Önizleme card and run it. The preview uses your unsaved draft mapping and writes nothing at all.
A dry run walks the real intake path yet stores nothing: no lead record, no welcome flow. Rows you have typed but not saved count towards the result too. That way you test a mapping without spending a live lead.
Before you start
- A tenant login that can open Ayarlar > Temel Bilgiler
- A sample JSON body your landing form actually posts
- Rows for phone and consent in the field map card; unsaved draft rows are enough
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Open the Dry-Run Önizleme card
Open Ayarlar > Temel Bilgiler and follow the "Landing Webhook Ayarları" link. Scroll down to the "Dry-Run Önizleme" card.
Paste your own payload and run it
Replace the ready-made JSON in the box with your own form body. Press "Dry Run Çalıştır". The button reads "Çalışıyor..." while the result panel on the right fills in.
Read the phone and consent lines in the result
Look for a green "Phone E.164" line holding the number in +90 form. "Onay alanı OK" should appear and the "would_upsert: true" badge should turn green. The "Çözümlenen alanlar" table below shows where each value landed.
Result checkIf it did not work
Check these
- "Payload bir JSON nesnesi olmalı." means you pasted an array or plain text. Paste a single object that opens with a brace.
- A red "Telefon normalize edilemedi" line means the phone key is mapped wrong or the number carries no country code. Type TR into the phone country hint box and run it again.
- "Onay alanı eksik / false" means consent never arrived, or arrived as false. Confirm that your form posts the consent checkbox as true.
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 29 August 2026.
