Form Lead Customers | LeadFlow AI documentation

Before you start

Use the account and workspace that own the records. This page does not include administrator configuration forms.

Open this feature

Open /portal/customers on your application domain, or use the matching item in the application menu.

Steps

Create segment

Open /portal/segments on your own application domain.
Complete these fields in that form: Segment name, Lifecycle stage, Minimum lead score, Tag. Their choices and limits are listed below.
Select Create segment. The exact label can change between creating and editing a record.
If validation fails, correct the named field and submit again. After success, reopen the same record and compare the saved values.

Field shown in the form	What to enter	Example / note
Segment name	Required. No more than 120 characters.	Test record (use a unique value where required).
Lifecycle stage	Optional, unless this form asks for it. Choose Any stage. No more than 80 characters.	Choose a displayed option; the available labels are listed above.
Minimum lead score	Optional, unless this form asks for it. Enter a whole number. At least 0. No more than 100.	Use the value required by the task; no example is assumed.
Tag	Optional, unless this form asks for it. Choose Any tag. No more than 80 characters.	Choose a displayed option; the available labels are listed above.

Create tag

Open /portal/tags on your own application domain.
Complete these fields in that form: Name, false. Their choices and limits are listed below.
Select Create tag. The exact label can change between creating and editing a record.
If validation fails, correct the named field and submit again. After success, reopen the same record and compare the saved values.

Field shown in the form	What to enter	Example / note
Name	Required. No more than 80 characters.	Test record (use a unique value where required).
false	Required. No more than 20 characters.	Use the value required by the task; no example is assumed.

Fields shown in the interface

Only fields traced to this role’s handler and its own view are listed. The application can show separate create/edit forms; do not fill every row on one screen.

Form 1 — fields shown in the interface

Field	What to enter or choose
Segment name	Required. No more than 120 characters.
Lifecycle stage	Optional, unless this form asks for it. Choose Any stage. No more than 80 characters.
Minimum lead score	Optional, unless this form asks for it. Enter a whole number. At least 0. No more than 100.
Tag	Optional, unless this form asks for it. Choose Any tag. No more than 80 characters.

Form 2 — fields shown in the interface

Field	What to enter or choose
Name	Required. No more than 80 characters.
false	Required. No more than 20 characters.

Check the result

After a source-checked procedure, verify the same record in the same workspace. Check saved values, visible state and access with the intended test account. An external payment/message/provider action needs its own result check.

Problems and validation

Problem	Next step
A field rejects the value	Check its named error, the form’s visible choices and the relevant limit. Do not substitute internal numeric codes for the displayed options.
The control is missing	Check role, plan, enabled app and current record state. Do not grant administrator access merely to complete a User task.
The saved result is unexpected	Reopen the same record and verify its owner/workspace before repeating the action.

Technical reference

Role-scoped source references

Pinned commit: 0a97c2b1d8022981713b1f32874690236dcf1610

Source-only route information

Method	Source-default route
LIVEWIRE	/portal/customers
LIVEWIRE	/portal/customers/{customer}
LIVEWIRE	/portal/segments
LIVEWIRE	/portal/tags
LIVEWIRE	/portal/activities