Custom Fields

What are custom fields?#

Custom fields allow you to capture data beyond the platform's native fields (email, phone, name, company, CNPJ). If your form collects information like "job title", "industry", "monthly revenue", or "number of employees", this data is stored as custom fields.

Fields sent via webhook that don't match any native alias (such as email, phone, nome, etc.) are automatically saved as custom fields. You don't need to map them manually.

Creating a custom field#

Access the fields page

In the sidebar menu, go to Leads > Custom Fields. You'll see a list of all custom fields already created in your workspace.

Create a new field

Click "New Field" and fill in:

Field name: the name displayed in the interface (e.g., "Job Title", "Industry")
Field type: choose from text, number, date, boolean (yes/no), or dropdown list

The field identifier (slug) is automatically generated from the name.

Save and use

Click "Save". The field will be immediately available to receive data via webhook and will be displayed in each lead's details.

Limits by plan#

The number of custom fields depends on your plan:

Plan	Custom fields
Starter	Up to 10 fields
Pro	Up to 25 fields
Scale	Unlimited

If you reach your plan's limit, new fields received via webhook will still be saved in the lead's raw payload, but they won't appear as structured fields until you upgrade or remove existing fields.

Automatic system suggestions#

When Zero Bad Leads receives data via webhook containing fields that haven't been registered yet, the system automatically suggests creating them. You'll see a notice on the custom fields page indicating new fields detected in the received data.

This makes setup easy: just receive a test lead and the system will indicate which custom fields to create.

How fields appear on the lead#

When you open a lead's details, you'll find a dedicated Custom Fields section. Values are displayed with the field's friendly name and formatted according to type (text, number, date, etc.).

Mapping with webhook data#

Custom fields work automatically with data received via webhook. The mapping follows these rules:

Exact match: if the field name in the webhook JSON matches the custom field's slug, the value is automatically associated
Alias match: you can add aliases to the field (e.g., field "Job Title" accepts cargo, job_title, position)
New field: if no match is found, the data is saved as a generic custom field

{
  "email": "joao@empresa.com",
  "nome": "João Silva",
  "cargo": "Diretor Comercial",
  "faturamento_mensal": "500000",
  "numero_funcionarios": "120"
}

In this example, email and nome are native fields. The rest (cargo, faturamento_mensal, numero_funcionarios) will be saved as custom fields.

Custom fields are workspace-specific. If you have multiple workspaces, each one will have its own fields.