All guides
User

Inbox 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
  1. Open /portal/inbox/automations on your site.

Steps

Choose a task

Use Save flow

  1. Open /portal/inbox/automations/builder/new on your application domain, using the workspace account for this task.
  2. Find the form containing Flow name, State, Channel. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save flow. 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.
FieldWhat to enter or choose
Flow nameEnter the flow name for this task, using the help or example shown by the form. The form’s example is VIP routing. Replace it with your own value.
StateChoose Draft, Live, Paused.
ChannelChoose All connected channels.
Keyword matchEnter the keyword match for this task, using the help or example shown by the form. Comma-separated. Any match starts the action path. The form’s example is refund, invoice. Replace it with your own value.
Only unassignedEnter the only unassigned for this task, using the help or example shown by the form. Preserve an existing agent owner.
Cooldown minutesEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0.
Set priorityChoose Low, Normal, High, Urgent, No priority change.
Assign teammateChoose Keep current assignment.
Internal noteEnter the internal note for this task, using the help or example shown by the form. The form’s example is Why this was routed…. Replace it with your own value.
Send messageEnter the send message for this task, using the help or example shown by the form. The form’s example is Write the automated reply…. Replace it with your own value.
Approved template nameEnter the approved template name for this task, using the help or example shown by the form. Template delivery currently requires an approved WhatsApp Cloud template on the conversation channel. The form’s example is welcome_message. Replace it with your own value.
Template languageEnter the template language for this task, using the help or example shown by the form. The form’s example is en_US. Replace it with your own value.
Template variablesEnter the template variables for this task, using the help or example shown by the form. Comma- or line-separated static values.
AI reply instructionsEnter the ai reply instructions for this task, using the help or example shown by the form. The AI workspace policy, consent checks, knowledge rules and monthly quota still apply. The form’s example is Answer briefly using approved Inbox AI policy…. Replace it with your own value.
Set conversation statusChoose Open, Pending, Resolved, No status change.
Move stageChoose New, Contacted, Qualified, Proposal, Won, Lost, No stage change.
Conversation tagEnter the conversation tag for this task, using the help or example shown by the form.
Tag modeChoose Add, Remove.
Wait secondsEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. The continuation is placed on the queue. A worker must be running for it to continue. Minimum 0. Maximum 604800.

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: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information
MethodSource-default route
GET/portal/inbox/automations
GET/portal/inbox/automations/builder/new
GET/portal/inbox/automations/builder/{rule}
Unmapped fields — not user instructions

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

Source keyHandler
form.post_idsmodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.notemodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.reply_bodymodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.public_comment_reply_bodymodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.private_comment_reply_bodymodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.template_variablesmodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.ai_instructionsmodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
form.tagmodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php
aiBriefmodules/Inbox/InboxAutomations/Livewire/InboxAutomationWorkspace.php