The Meta Relay tab, inside Platform Settings, forwards the original WhatsApp Meta webhook body and signature headers to a second target URL, without changing the platform’s existing webhook integration. This is used when a self-hosted instance needs to mirror raw Meta webhook traffic to another system.This tab is only visible on self-hosted / self-managed instances. It does not appear in Platform Settings on managed (non self-managed) platforms.
Enter the forward URL that should receive the forwarded raw Meta webhook payloads
Enter a verify token, used only by the manual verification test (not used for live forwarded events)
Turn the relay on or off entirely
Choose which event types to forward: messages, statuses (sent/delivered/read and other status webhooks), and account updates (business account review/alert events)
Run a Test Verification to check whether the target server accepts the expected Meta challenge flow
Send a Meta-Style Sample payload to the target URL to confirm it can receive and process forwarded webhooks
Review relay health at a glance: last attempt, last success, last failure, and recent entry count
Review the Recent Relay Attempts list (today’s latest 10 attempts), each showing type, success/failure, timestamp, HTTP status, whether the payload was signed, target URL, forwarded event types, and a response preview
Open Platform Settings from the Platform sidebar and select the Meta Relay tab. This tab only appears on self-managed/self-hosted instances.
Click Edit in the top-right to make the fields editable.
Enter the Forward URL — the endpoint that should receive the forwarded raw Meta webhook.
Enter the Verify Token used for the manual verification probe.
Toggle Relay Enabled on to activate forwarding.
Under Relay Scope, toggle on the event types you want forwarded: Forward Messages, Forward Statuses, and Forward Account Updates. These toggles are only active once the relay itself is enabled.
Click Save to store your changes.
Click Test Verification to confirm the target server correctly handles Meta’s verification challenge (requires both the forward URL and verify token to be filled in).
Click Send Meta-Style Sample to send a sample Meta-formatted webhook to the target URL and confirm it’s received correctly.
Scroll down to Recent Relay Attempts to review the outcome of live forwards and test sends, including HTTP status and response preview for each attempt.
The Meta Relay tab is missing. It only appears on self-managed instances. If your instance should be self-managed and the tab is missing, reload the page — a single failed license check while the page loads can hide the tab until you refresh. If it’s still missing, contact support.
Save is blocked with “Webhook URL Required.” You can’t turn the relay on without a Forward URL. The Verify Token isn’t required to save.
Test Verification is disabled but Send Meta-Style Sample works. This is expected. Test Verification needs both the Forward URL and the Verify Token, while Send Meta-Style Sample only needs the Forward URL. Fill in the Verify Token to enable the verification test.
The Relay Scope toggles are greyed out. They’re locked whenever you’re not in edit mode, and also whenever Relay Enabled is off. Click Edit, turn Relay Enabled on, then choose which events to forward.
I can’t find an older relay attempt.Recent Relay Attempts shows only today’s latest 10 attempts, and older ones aren’t shown.
Changing the Verify Token doesn’t affect live traffic. Live forwards always keep the original Meta body and signature headers. The Verify Token is used only by the manual Test Verification check, so changing it doesn’t require re-verifying anything for real events to keep flowing.
