All guides
User

AI Workflows

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/automation on your site.

Steps

Choose a task

Use Check setup & retry

  1. Open /portal/automation/runs on your application domain, using the workspace account for this task.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Select Check setup & retry. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 1d0944d30f606782c9abf5b878224cdd3cd09b99

Source-only route information
MethodSource-default route
LIVEWIRE/portal/automation
LIVEWIRE/portal/automation/workflows
LIVEWIRE/portal/automation/templates
LIVEWIRE/portal/automation/runs
LIVEWIRE/portal/automation/workflows/builder/new
LIVEWIRE/portal/automation/workflows/{workflow}/edit