Disconnect, update credentials, app secret: what each does

What Beacon Messenger's WhatsApp page does when you disconnect, rotate a token or save without the app secret, and why the verify token never changes.

Connecting a WhatsApp Business account is a one-time job that most merchants do once and forget. The page it lives on, however, has three more controls that get used at the worst possible moments: when a token has been revoked, when a Meta app has been rebuilt, or when someone is leaving the company and the credentials they created have to go with them. Those are not moments for guessing what a button does.

This post goes through the WhatsApp account page in Beacon Messenger after the first connection: the Disconnect button, the Update credentials form, the App secret missing banner, and the webhook card with its callback URL and verify token. For what the first Connect checks, see the test message post; this one picks up where it ends.

What Disconnect removes, and what it keeps

The Disconnect button sits beside Refresh templates on the connected number card and asks for confirmation with a plain warning: automations will stop sending until you reconnect. Confirming clears the connection record in one write. Gone are the WhatsApp Business Account ID, the phone number ID, the display phone and verified name, the quality rating, the encrypted access token, the encrypted app secret, the cached template list and its last-synced time, and the connected-at timestamp. The page returns to the empty connect form.

What is deliberately not touched:

  • Your automations. Each trigger keeps its enabled state, its template name, its variable mapping and its delay settings, so reconnecting does not mean rebuilding them.
  • The message log and the audit log. Every row stays, including the WhatsApp message IDs that delivery statuses are matched against.
  • The webhook verify token and therefore the callback URL. More on that below.
  • Plan and usage. Disconnecting does not reset the month's message count.

While disconnected, the automations keep running in the sense that Shopify events are still received and evaluated. Each one that would have sent a message is written to the Messages page as a skipped row with the reason Not connected, together with the template name it would have used and the order context it would have filled it with. That stored context is what makes the Retry button on those rows work: once you reconnect, you can resend the notifications that were skipped, one by one, from the Messages page. Abandoned checkouts behave the same way; their timers still run and the message is skipped, not lost, when the timer fires.

Update credentials is Connect again, with one trap

The Update credentials button at the top of the page opens the same four-field form as the first connection, with the WhatsApp Business Account ID and phone number ID prefilled and the two secret fields empty. Saving runs the full connect sequence described in the earlier post: the IDs must be numeric, the token at least twenty characters, the phone number lookup must succeed, templates are reloaded, the webhook subscription is re-requested, and the new values replace the old ones with a fresh connected-at time. If the phone number lookup fails, nothing is replaced; the old connection stays as it was.

The trap is the App secret field. It is optional on the form, it is never prefilled, and saving replaces whatever was stored with whatever is in the field. Rotate the access token and leave the app secret blank, and you have just removed the app secret you entered six months ago. The page tells you immediately with a warning banner headed App secret missing, but it is worth knowing in advance: every time you save credentials, paste the app secret again as well. It has not changed, unless you reset it in Meta, but the app has no way to know that.

Error messages on save come straight from Meta, with a hint appended for the three common codes: 190 means the token is invalid or expired and you should generate a permanent system-user token; 100 means one of the two IDs is wrong; 10 or 200 mean the token exists but lacks the whatsapp_business_messaging or whatsapp_business_management permission.

What the app secret is for

Meta signs every webhook it sends with an HMAC of the request body, keyed with your Meta app's secret, and puts the result in the X-Hub-Signature-256 header. Beacon Messenger recomputes that HMAC over the raw body and compares it with the header in constant time; a mismatch is answered with 401 and the payload is not processed. That check is the only way to tell a genuine delivery receipt or a genuine Confirm reply from a request anyone on the internet could POST to your callback URL. Without the secret, the check cannot be performed, which is what the banner is warning you about: the secret protects the delivery statuses and the cash-on-delivery replies, and it is the one field on the form that defends your store rather than enabling a feature.

The secret lives in Meta for Developers under your app's Settings, then Basic, behind a Show button. It is encrypted at rest in Beacon Messenger with a key held outside the database, like the access token, and it is never displayed back to you. If you suspect it has leaked, reset it in Meta and save the new one through Update credentials, remembering to paste the token too.

The verify token is yours for life

The Webhook card shows two read-only values with Copy buttons: a callback URL and a verify token. They are generated once, when your store first installs the app, and they never change: not on disconnect, not on Update credentials, not on reinstall of a store the app already knows. The callback URL is the app's address followed by a path that ends in the token itself, so the URL and the token are two views of the same secret.

That design has a practical consequence. The Meta side of the webhook, the URL and token you paste into WhatsApp, then Configuration, in your Meta app, is a one-time setup. Rotating tokens, swapping phone numbers, disconnecting and reconnecting all leave it valid. The only time you touch it again is when you move to a different Meta app, and even then it is the same two values pasted into a new place.

What the callback endpoint does with each request
RequestCheckResponse
GET with hub.mode=subscribehub.verify_token must equal your token; the token in the path must belong to a storeEchoes hub.challenge, which completes Meta's verification
GET with anything elseFails the above403 Forbidden
POST, unknown token in pathNo store has this token404 Not found
POST, signature does not match the stored app secretHMAC over the raw body differs from X-Hub-Signature-256401 Invalid signature, nothing processed
POST, validEvents for a different phone number ID than yours are ignored; statuses update log rows, Confirm or Cancel replies tag the order200 ok, even if processing fails, so Meta does not retry for hours

The last row matters for debugging. A webhook that reached the app but hit an error inside is still acknowledged, because Meta otherwise resends the same event repeatedly, and the failure is written to the server log instead. If delivery statuses stop arriving, the first things to check are therefore not the app but the Meta side: is the subscription still active on the WABA, is the messages field ticked, and does the callback URL in Meta match the one on the card character for character.

Three scenarios, in order of how often they happen

  1. A token stops working. Rows on the Messages page fail with Meta's code 190. Create a new permanent system-user token in Meta Business settings, open Update credentials, paste the token and the app secret, save. Then retry the failed rows from the Messages page; their stored context sends them as they would have been sent.
  2. Someone leaves. If they created the system user, create a new system user and token under an account that stays, and save it as above. The old token can then be revoked in Meta without any gap. Do not disconnect first; a disconnect skips every message in between, while an update replaces the token atomically.
  3. You are moving to a new Meta app or a new WABA. Disconnect, so the old IDs are gone, then connect with the new values. Paste the same callback URL and verify token into the new app's webhook configuration and subscribe to messages. Your automations and templates mapping are still there; press Refresh templates and check that the names your automations use exist in the new account, because a template missing in the new WABA is the usual reason the first message after a move is skipped.

None of these should take more than ten minutes, and none of them require touching an automation. The account page separates the pieces that change, tokens and secrets, from the pieces that should not, the webhook address and your configuration, and the delivery check post is the place to go once the new credentials are in to confirm statuses are flowing again.

Frequently asked questions

What happens to my automations if I disconnect the WhatsApp account?

They keep their settings but every message they would send is logged as skipped with the reason Not connected, including the order context. After you reconnect, each skipped row on the Messages page has a Retry button that sends it from that stored context, so nothing is lost, only delayed.

Why does Beacon Messenger say my app secret is missing after I updated the token?

The App secret field on the Update credentials form is optional and never prefilled, and saving replaces the stored secret with the field's contents. Saving with it blank removes the secret. Open Update credentials again and paste both the token and the app secret from Meta for Developers, Settings, Basic.

Do I need to change the webhook in Meta when I rotate my access token?

No. The callback URL and verify token are generated once per store and survive disconnects, credential updates and reinstalls. Only the access token and app secret change on the Beacon Messenger side; the Meta webhook configuration stays valid as long as you are using the same Meta app.

Why do webhook requests return 200 even when something went wrong inside the app?

Meta retries any non-2xx response for hours, which would flood the app with duplicates of an event that would fail again. The app verifies the signature and the token, then acknowledges the request and logs any processing error on the server, where it can be fixed without a retry storm.

More guides