User
WhatsApp Developer
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-hub/developer on your site.
Steps
Choose a task
Use Create key
- Open /portal/whatsapp-hub/developer on your application domain, using the workspace account for this task.
- Find the form containing Key name, e.g. CRM production. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
- Select Create key. 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 |
|---|---|
| Key name, e.g. CRM production | Required. Enter the key name, e.g. crm production for this task, using the help or example shown by the form. The form’s example is Key name, e.g. CRM production. Replace it with your own value. Maximum 120 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: 37d44a1727216f5c492205024b323aa522730ebc
Source-only route information
| Method | Source-default route |
|---|---|
| POST | /api/v1/whatsapp/messages |
| LIVEWIRE | /portal/whatsapp-hub/developer |
Unmapped fields — not user instructions
These fields belong to this role’s source handler, but their screen labels were not confirmed.
| Source key | Handler |
|---|---|
| keyName | modules/WhatsappCRM/WhatsappCrmDeveloper/Livewire/WhatsappDeveloperWorkspace.php |
| conversation_id | modules/WhatsappCRM/WhatsappCrmDeveloper/Http/Controllers/WhatsappHubApiController.php |
| body | modules/WhatsappCRM/WhatsappCrmDeveloper/Http/Controllers/WhatsappHubApiController.php |