Map landing-form fields to Chatinbox fields
Connect the keys your landing form posts to Chatinbox canonical fields. A lead is accepted only when name, phone and consent each have a row.
The Alan Eşlemesi card turns the keys your form sends into names Chatinbox recognises. A lead is accepted only when three canonical fields are mapped: name, phone and consent. Kaydet checks only phone and consent; it also saves without a name row, but incoming leads are then rejected. A red line names the missing field the card checks for.
Before you start
- A tenant login that can open the Ayarlar tab
- A sample JSON body from your landing form
- One form field each for the name, the phone number and consent
- A key generated at least once on the API Anahtarı card; otherwise the mapping is not saved
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 Alan Eşlemesi card
Follow the "Landing Webhook Ayarlari" link on the Ayarlar page.
Type the form key in the left column
Copy the key from your sample JSON body.
Pick its counterpart on the right
Use the Satır Ekle button for another pair.
Add a hint for local phone formats
Type TR into the Telefon Ülke İpucu box.
Save and check the history card
A summary line with the row count lands on the card at the right.
Result checkIf it did not work
Check these
- If Kaydet will not click, read the red box above the button; it lists what blocks the save, such as a missing mandatory field or a row with no counterpart picked. Kaydet also stays greyed out when you have changed nothing.
- Two rows pointing at the same canonical field raise an error. Delete the extra row.
- Several rows may point at metadata, but only the last one is kept when you save.
- On a server-change warning, return to the current state with Sunucu halini yükle and redo the edit.
- If saving worked but no lead reaches the panel, check that the name row is mapped; a lead arriving without a name mapping is rejected.
- If "row_version missing — refetch first" appears after you press Kaydet, no key has been generated yet. Press Yeni API Anahtarı Oluştur on the API Anahtarı card first, then press Kaydet again.
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 4 October 2026.
