Troubleshooting, verified limitations and release history

Understand the no public connector limitation

There is no supported public remote connector URL or administrator-exposed port/token configuration. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Administrators, support staff and deployment engineersPermission: Relevant module or administrator permissionModule v1.0.0 · 2026.07.30-r20.5

Jump to steps

Where to goAdmin Area → WhatsApp → Connections / Inbox / Settings / Audit Trail

Before you start

Verify the module is active and select the intended WhatsApp account before changing any operational record.
Use an account with the stated native CRM capability and per-account access.
Test with controlled customer/contact data before relying on live verification, email or CRM automation.

What you’ll accomplish

There is no supported public remote connector URL or administrator-exposed port/token configuration. These instructions follow the supplied r20.5 controller, model, view, installer, connector and automation flow.

Follow these steps

Go to Admin Area → WhatsApp → Connections / Inbox / Settings / Audit Trail.
Find the account, conversation, setting, session or evidence relevant to “Understand the no public connector limitation”.
Check the displayed value or behaviour against this guide’s code-backed rules.
Do not change unrelated account, CRM or connector settings while verifying the result.
Verify the expected state in the related Inbox, Connections, customer history, native CRM record or Audit Trail.

Fields and options to review

Connection status and preparation messageConnection status and preparation message

Audit action and verification sessionAudit action and verification session

Account permissionsAccount permissions

Saved settings and limitsSaved settings and limits

CRM email/cron configurationCRM email/cron configuration

Rules the system enforces

Troubleshoot through the supported CRM controls before changing runtime files.
Do not delete session directories or database records manually.
Verified limitations are documented so users do not search for nonexistent menus or integrations.
There is no supported public remote connector URL or administrator-exposed port/token configuration.

How to confirm 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.

Was this guide useful?Your response is stored only in this browser.