All guides
User

WhatsApp Unofficial 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/whatsapp-unofficial/automations on your site.

Steps

Use Save flow

  1. Open /portal/whatsapp-unofficial/automations/builder/new on your application domain, using the workspace account for this task.
  2. Find the form containing Flow name, Inbound keyword, Sending device. 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 Welcome keyword reply. Replace it with your own value.
Inbound keywordEnter the inbound keyword for this task, using the help or example shown by the form. A real inbound message must contain this text. The form’s example is hello. Replace it with your own value.
Sending deviceEnter the sending device for this task, using the help or example shown by the form.
Contact group (optional)Choose All opted-in contacts.
Default template (optional)Enter the default template (optional) for this task, using the help or example shown by the form.
Wait minutesEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Used by the Wait node. A persistent queue worker is required for live execution. Minimum 0. Maximum 10080.

Use Pause

  1. Open /portal/whatsapp-unofficial/automations/builder/new on your application domain, using the workspace account for this task.
  2. Find the form containing Flow name, Inbound keyword, Sending device. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Pause. 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 Welcome keyword reply. Replace it with your own value.
Inbound keywordEnter the inbound keyword for this task, using the help or example shown by the form. A real inbound message must contain this text. The form’s example is hello. Replace it with your own value.
Sending deviceEnter the sending device for this task, using the help or example shown by the form.
Contact group (optional)Choose All opted-in contacts.
Default template (optional)Enter the default template (optional) for this task, using the help or example shown by the form.
Wait minutesEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Used by the Wait node. A persistent queue worker is required for live execution. Minimum 0. Maximum 10080.

Use Generate draft

  1. Open /portal/whatsapp-unofficial/automations/builder/new on your application domain, using the workspace account for this task.
  2. Find the form containing Flow name, Inbound keyword, Sending device. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Generate draft. 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 Welcome keyword reply. Replace it with your own value.
Inbound keywordEnter the inbound keyword for this task, using the help or example shown by the form. A real inbound message must contain this text. The form’s example is hello. Replace it with your own value.
Sending deviceEnter the sending device for this task, using the help or example shown by the form.
Contact group (optional)Choose All opted-in contacts.
Default template (optional)Enter the default template (optional) for this task, using the help or example shown by the form.
Wait minutesEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Used by the Wait node. A persistent queue worker is required for live execution. Minimum 0. Maximum 10080.
Describe the flowRequired. Enter the describe the flow for this task, using the help or example shown by the form. The form’s example is When an opted-in customer sends hello, wait five minutes, send a welcome template, then record the run.. 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

  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/whatsapp-unofficial/automations
GET/portal/whatsapp-unofficial/automations/builder/new
GET/portal/whatsapp-unofficial/automations/builder/{automation}