All guides
User

Form Lead Automation

Run a defined action when its configured trigger and conditions match.

Step-by-step guide

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/workflows on your application domain, or use the matching item in the application menu.

Steps

Create workflow

  1. Open /portal/workflows on your own application domain.
  2. Complete these fields in that form: Name, Description, Trigger, Only this form. Their choices and limits are listed below.
  3. Select Create workflow. The exact label can change between creating and editing a record.
  4. 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 formWhat to enterExample / note
NameRequired. No more than 255 characters.Test record (use a unique value where required).
DescriptionOptional, unless this form asks for it. No more than 1000 characters.A short description of this test record.
TriggerRequired. Choose Form submitted, Lead created, Tag added, No activity, Partial submission stale.Choose a displayed option; the available labels are listed above.
Only this formOptional, unless this form asks for it. Choose Any form. Leave blank to match every form.Choose a displayed option; the available labels are listed above.

Save changes

  1. Open /portal/workflows on your own application domain.
  2. Complete these fields in that form: Name, Description, Trigger, Only this form. Their choices and limits are listed below.
  3. Select Save changes. The exact label can change between creating and editing a record.
  4. 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 formWhat to enterExample / note
NameRequired. No more than 255 characters.Test record (use a unique value where required).
DescriptionOptional, unless this form asks for it. No more than 1000 characters.A short description of this test record.
TriggerRequired. Choose Form submitted, Lead created, Tag added, No activity, Partial submission stale.Choose a displayed option; the available labels are listed above.
Only this formOptional, unless this form asks for it. Choose Any form. Leave blank to match every form.Choose a displayed option; the available labels are listed above.

Create email automation

  1. Open /portal/email-automation on your own application domain.
  2. Complete these fields in that form: Rule name, Internal description, Only this form, Recipient, Subject, Email body. Their choices and limits are listed below.
  3. Select Create email automation. The exact label can change between creating and editing a record.
  4. 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 formWhat to enterExample / note
Rule nameRequired. No more than 255 characters.Test record (use a unique value where required).
Internal descriptionOptional, unless this form asks for it. No more than 1000 characters.A short description of this test record.
Only this formOptional, unless this form asks for it. Choose Any form.Choose a displayed option; the available labels are listed above.
RecipientRequired. Choose Lead email, Team inbox.Choose a displayed option; the available labels are listed above.
SubjectRequired. No more than 160 characters.Use the value required by the task; no example is assumed.
Email bodyRequired. No more than 2000 characters.Use the value required by the task; no example is assumed.

Create webhook

  1. Open /portal/webhooks on your own application domain.
  2. Complete these fields in that form: Webhook name, Internal description, Only this form, Endpoint URL, Method, Signing secret. Their choices and limits are listed below.
  3. Select Create webhook. The exact label can change between creating and editing a record.
  4. 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 formWhat to enterExample / note
Webhook nameRequired. No more than 255 characters.Test record (use a unique value where required).
Internal descriptionOptional, unless this form asks for it. No more than 1000 characters.A short description of this test record.
Only this formOptional, unless this form asks for it. Choose Any form.Choose a displayed option; the available labels are listed above.
Endpoint URLRequired. Enter a complete URL, including https:// where appropriate. No more than 500 characters.https://example.test/demo (replace with your own test destination).
MethodRequired. Choose POST, PUT, PATCH.Choose a displayed option; the available labels are listed above.
Signing secretOptional, unless this form asks for it. No more than 255 characters. Enter the real value privately; do not put it in a screenshot or support message.Use the value appropriate to your test account; no preset is supplied.

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
FieldWhat to enter or choose
Rule nameRequired. No more than 255 characters.
Internal descriptionOptional, unless this form asks for it. No more than 1000 characters.
Only this formOptional, unless this form asks for it. Choose Any form.
RecipientRequired. Choose Lead email, Team inbox.
SubjectRequired. No more than 160 characters.
Email bodyRequired. No more than 2000 characters.
Form 2 — fields shown in the interface
FieldWhat to enter or choose
Webhook nameRequired. No more than 255 characters.
Internal descriptionOptional, unless this form asks for it. No more than 1000 characters.
Only this formOptional, unless this form asks for it. Choose Any form.
Endpoint URLRequired. Enter a complete URL, including https:// where appropriate. No more than 500 characters.
MethodRequired. Choose POST, PUT, PATCH.
Signing secretOptional, unless this form asks for it. No more than 255 characters. Enter the real value privately; do not put it in a screenshot or support message.
Form 3 — fields shown in the interface
FieldWhat to enter or choose
NameRequired. No more than 255 characters.
DescriptionOptional, unless this form asks for it. No more than 1000 characters.
TriggerRequired. Choose Form submitted, Lead created, Tag added, No activity, Partial submission stale.
Only this formOptional, unless this form asks for it. Choose Any form. Leave blank to match every form.

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

ProblemNext step
A field rejects the valueCheck 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 missingCheck role, plan, enabled app and current record state. Do not grant administrator access merely to complete a User task.
The saved result is unexpectedReopen 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
MethodSource-default route
LIVEWIRE/portal/workflows
LIVEWIRE/portal/email-automation
LIVEWIRE/portal/webhooks
LIVEWIRE/portal/automation-logs
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
segmentIdmodules/AppFormLeadAutomation/Livewire/FormLeadWorkflows.php
builderActionsmodules/AppFormLeadAutomation/Livewire/FormLeadWorkflows.php