User
WhatsApp Notification
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/whatsapp-notification/automations on your site.
Steps
Create or update: Update automation / Save automation
- Open /portal/whatsapp-notification/automations on your application domain, using the workspace account for this task.
- Find the form containing Name, Business, Trigger. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
- Use the button shown for the current state: Update automation, Save automation. Creation and editing can show different labels; submit the form once.
- 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 |
|---|---|
| Name | Required. Enter the name for this task, using the help or example shown by the form. The form’s example is Booking confirmation. Replace it with your own value. Maximum 255 characters. |
| Business | Optional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. |
| Trigger | Required. Enter the trigger for this task, using the help or example shown by the form. |
| WhatsApp template | Required. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. |
| Timing | Required. Choose Immediately, After delay, Before booking time. |
| Delay value | Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. |
| Unit | Required. Choose Minutes, Hours, Days. |
| Recipient | Required. Choose Customer, Business owner, Custom WhatsApp. |
| Custom phone | Optional unless the current form requests it. Enter the custom phone for this task, using the help or example shown by the form. The form’s example is 15551234567. Replace it with your own value. Maximum 40 characters. |
| Status | Required. Choose Draft, Active, Inactive. |
| Require customer phone | Enter the require customer phone for this task, using the help or example shown by the form. Skip customer messages when no phone exists. |
| Phone Number ID | Required. Enter the phone number id for this task, using the help or example shown by the form. Maximum 100 characters. |
| Access token | Required. Enter the value privately from your account or the service configuration. Do not use sample credentials from a guide. Maximum 2000 characters. |
| Approved template name | Optional unless the current form requests it. Enter the approved template name for this task, using the help or example shown by the form. The form’s example is Optional. Replace it with your own value. Maximum 255 characters. |
| Template language | Required. Enter 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. Maximum 12 characters. |
| Field | Optional unless the current form requests it. Enter the field for this task, using the help or example shown by the form. Maximum 80 characters. |
| Operator | Required. Enter the operator for this task, using the help or example shown by the form. |
| Value | Optional unless the current form requests it. Enter the value for this task, using the help or example shown by the form. Maximum 255 characters. |
Use Save template
- Open /portal/whatsapp-notification/templates on your application domain, using the workspace account for this task.
- Find the form containing Name, Business, Type. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
- Select Save template. 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 |
|---|---|
| Name | Required. Enter the name for this task, using the help or example shown by the form. Maximum 255 characters. |
| Business | Optional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. |
| Type | Required. 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. Maximum 80 characters. |
| Language | Required. Enter the language for this task, using the help or example shown by the form. Maximum 12 characters. |
| Approved template name | Optional unless the current form requests it. Enter the approved template name for this task, using the help or example shown by the form. The form’s example is Optional. Replace it with your own value. Maximum 255 characters. |
| Body | Required. Enter the body for this task, using the help or example shown by the form. Maximum 4096 characters. |
| Meta body parameter mapping | Optional unless the current form requests it. Enter the meta body parameter mapping for this task, using the help or example shown by the form. The form’s example is 1={customer_name} 2={booking_date} 3={booking_time}. Replace it with your own value. Maximum 12000 characters. |
| Meta header type | Required. Choose No dynamic header, Text, Image, Video, Document. |
| Header value / Public media URL or media ID | Optional unless the current form requests it. Enter the complete address required by this field. For a callback or webhook, copy the URL shown by the running application instead of guessing its path. Maximum 4096 characters. |
| Upload media instead | Choose a file from your computer. Use the type requested by this upload control. |
| Document filename | Optional unless the current form requests it. Enter the document filename for this task, using the help or example shown by the form. The form’s example is invoice.pdf. Replace it with your own value. Maximum 255 characters. |
| Dynamic button mapping | Optional unless the current form requests it. Enter the dynamic button mapping for this task, using the help or example shown by the form. The form’s example is 0|url|{google_review_url} 1|quick_reply|confirm-booking. Replace it with your own value. Maximum 12000 characters. |
| Status | Required. Choose Active, Inactive. |
Use New automation
- Open /portal/whatsapp-notification/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 New automation. 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 Resend
- Open /portal/whatsapp-notification/logs 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 Resend. 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 New template
- Open /portal/whatsapp-notification/templates 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 New template. 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.
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: 5af0236c6d99c50079f5ab8b8fb035506634bd8d
- modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php
- modules/AppWhatsAppNotification/Livewire/LogsIndex.php
- modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php
- modules/AppWhatsAppNotification/resources/views/automations.blade.php
- modules/AppWhatsAppNotification/resources/views/logs.blade.php
- modules/AppWhatsAppNotification/resources/views/partials/automation-dialogs.blade.php
- modules/AppWhatsAppNotification/resources/views/partials/template-dialogs.blade.php
- modules/AppWhatsAppNotification/resources/views/templates.blade.php
Source-only route information
| Method | Source-default route |
|---|---|
| GET | /portal/whatsapp-notification/automations |
| GET | /portal/whatsapp-notification/templates |
| GET | /portal/whatsapp-notification/logs |
Unmapped fields — not user instructions
These fields belong to this role’s source handler, but their screen labels were not confirmed.
| Source key | Handler |
|---|---|
| business_id | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| name | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| trigger_event | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| status | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| delay_type | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| delay_unit | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| whatsapp_template_id | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| send_to | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| custom_phone | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| phone_number_id | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| template_name | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| template_language | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| condition_field | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| condition_operator | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| condition_value | modules/AppWhatsAppNotification/Livewire/AutomationsIndex.php |
| business_id | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| name | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| type | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| template_name | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| language | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| body | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| body_parameter_map | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| header_type | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| header_value | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| header_filename | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| button_parameter_map | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| status | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| image | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| video | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |
| document | modules/AppWhatsAppNotification/Livewire/TemplatesIndex.php |