User

Web Push Automations

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

Open /portal/web-push/automations on your site.

Steps

Choose a task

Run now
Pause
v
Generate draft

Use Run now

Open /portal/web-push/automations on your application domain, using the workspace account for this task.
Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
Select Run now. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Use Pause

Open /portal/web-push/automations/builder/new on your application domain, using the workspace account for this task.
Find the form containing Flow name, Trigger, Event name. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Pause. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Flow name	Enter the flow name for this task, using the help or example shown by the form. The form’s example is Recover inactive subscribers. Replace it with your own value.
Trigger	Choose Subscriber created, Subscriber inactive for 30 days, Manual run, Custom API event.
Event name	Enter the event name for this task, using the help or example shown by the form. The form’s example is cart_abandoned. Replace it with your own value.
Audience segment	Enter the audience segment for this task, using the help or example shown by the form.
Default campaign	Enter the default campaign for this task, using the help or example shown by the form.
Delay minutes	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 10080.
Cooldown hours	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 720.
Timezone	Choose an available entry by its displayed name. The list depends on your account and the selected workspace; do not type an internal record ID.
Quiet start	Enter the quiet start for this task, using the help or example shown by the form.
Quiet end	Enter the quiet end for this task, using the help or example shown by the form.
Max per subscriber / 24h	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 50.
Stop after goal	Choose Opened, Clicked, Conversion, No goal stop.
Goal window days	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 365.

Use v

Open /portal/web-push/automations/builder/new on your application domain, using the workspace account for this task.
Find the form containing Flow name, Trigger, Event name. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select v. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Flow name	Enter the flow name for this task, using the help or example shown by the form. The form’s example is Recover inactive subscribers. Replace it with your own value.
Trigger	Choose Subscriber created, Subscriber inactive for 30 days, Manual run, Custom API event.
Event name	Enter the event name for this task, using the help or example shown by the form. The form’s example is cart_abandoned. Replace it with your own value.
Audience segment	Enter the audience segment for this task, using the help or example shown by the form.
Default campaign	Enter the default campaign for this task, using the help or example shown by the form.
Delay minutes	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 10080.
Cooldown hours	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 720.
Timezone	Choose an available entry by its displayed name. The list depends on your account and the selected workspace; do not type an internal record ID.
Quiet start	Enter the quiet start for this task, using the help or example shown by the form.
Quiet end	Enter the quiet end for this task, using the help or example shown by the form.
Max per subscriber / 24h	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 50.
Stop after goal	Choose Opened, Clicked, Conversion, No goal stop.
Goal window days	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 365.

Use Generate draft

Open /portal/web-push/automations/builder/new on your application domain, using the workspace account for this task.
Find the form containing Flow name, Trigger, Event name. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Generate draft. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Flow name	Enter the flow name for this task, using the help or example shown by the form. The form’s example is Recover inactive subscribers. Replace it with your own value.
Trigger	Choose Subscriber created, Subscriber inactive for 30 days, Manual run, Custom API event.
Event name	Enter the event name for this task, using the help or example shown by the form. The form’s example is cart_abandoned. Replace it with your own value.
Audience segment	Enter the audience segment for this task, using the help or example shown by the form.
Default campaign	Enter the default campaign for this task, using the help or example shown by the form.
Delay minutes	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 10080.
Cooldown hours	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 720.
Timezone	Choose an available entry by its displayed name. The list depends on your account and the selected workspace; do not type an internal record ID.
Quiet start	Enter the quiet start for this task, using the help or example shown by the form.
Quiet end	Enter the quiet end for this task, using the help or example shown by the form.
Max per subscriber / 24h	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 50.
Stop after goal	Choose Opened, Clicked, Conversion, No goal stop.
Goal window days	Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 365.
Describe the outcome	Required. Enter the describe the outcome for this task, using the help or example shown by the form. The form’s example is Example: When checkout is abandoned, wait 30 minutes, notify the matching cart segment, stop after conversion, and cap frequency to one per day.. Replace it with your own value. Maximum 2000 characters.

Fields and choices

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

Check the result

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
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

Problem	What to check
The screen or action is missing	Check the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read 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 empty	Check 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 pending	Check 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: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information

Method	Source-default route
GET	/portal/web-push/automations
GET	/portal/web-push/automations/builder/new
GET	/portal/web-push/automations/{automation}/edit
GET	/portal/web-push/automations/{automation}

Unmapped fields — not user instructions

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

Source key	Handler
aiBrief	modules/WebPush/WebPushAutomations/Livewire/AutomationWorkspace.php
form.quiet_hours_start	modules/WebPush/WebPushAutomations/Livewire/AutomationWorkspace.php
form.quiet_hours_end	modules/WebPush/WebPushAutomations/Livewire/AutomationWorkspace.php