Verify runtime readiness without exposing secrets

Follow this guide to use the connection status and QR/status panels rather than reading connector tokens or authentication files.

What this guide helps you do

Use the connection status and QR/status panels rather than reading connector tokens or authentication files. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

1. Go to Admin Area → WhatsApp → Connections.
2. Select the correct account, conversation, customer, staff member or session before you verify runtime readiness without exposing secrets.
3. Complete the visible fields and confirmation prompts exactly as described below.
4. Select the available action once and wait for its success or validation response.
5. Check the result in the operational record and, where applicable, in Audit Trail or the linked native CRM record.

Fields and options

Rules and limits

• Normal administrators are not asked for SSH, Node.js, ports, URLs, tokens or system services.
• Runtime operations are constrained to module-managed paths and loopback connector endpoints.
• Preparation, repair and build upgrade preserve the retained WhatsApp session unless Unlink or Delete is explicitly confirmed.
• Use the connection status and QR/status panels rather than reading connector tokens or authentication files.

Check it worked

• The requested action completes without a permission, validation, connector or native CRM error.
• The selected account or conversation shows the expected state without changing another account’s data.
• Where the action creates evidence, confirm the message, native record, verification event, portal history or audit entry is present.

Security, privacy and troubleshooting checks

• Never expose connector tokens, loopback ports, authentication directories or raw customer verification replies.
• Use the supported Connections, Access Control, Settings and Audit Trail pages rather than editing runtime or database records directly.
• If the expected control is missing, verify both native capability and per-account permission before treating it as an installation fault.

Related guides