New Flow Builder and Knowledge Base are live. What changed

Map landing-form fields to Chatinbox fields

Connect the keys your landing form posts to Chatinbox canonical fields. Save stays locked until phone and consent each have their own row.

Short answer

The field map card turns the keys your form sends into names Chatinbox recognises. Two canonical fields are mandatory: phone and consent. Leave one out and save stays greyed out. A red line names what is missing.

This page also exists in Turkish with the same scope: Türkçe okuyun

Before you start

  • A tenant login that can open the settings tab
  • A sample JSON body from your landing form
  • One form field for the phone number and one for consent

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 field map card

Follow the landing webhook link on the settings 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 add-row button for another pair.

Add a hint for local phone formats

Type TR into the phone country hint box.

Save and check the history card

A summary line with the row count lands on the card at the right.

Result check

If it did not work

Check these

  • If save will not click, hover it; the tooltip names the missing mandatory field.
  • Two rows pointing at the same canonical field raise an error. Delete the extra row.
  • Only metadata may repeat across rows.
  • On a server-change warning, load the server state and redo the edit.

Does this step look different in your panel?

We can review the screen and exact error text together.

Write to support

This guide was checked against the product UI and code inventory on 29 August 2026.

Chatinbox chatinbox

Looking into Chatinbox? I answer setup, pricing and channel questions right here.