Create a WhatsApp System User access token

Use a System User credential for the ongoing WhatsApp connection. The token offered in Meta's test screen is temporary and should not be mistaken for the operational credential. A token configured without scheduled expiry, when Meta offers that choice, can still be revoked or lose asset access.

1. Prepare the app and WhatsApp account

Complete app creation and the WhatsApp use-case setup. Confirm the app and WhatsApp Business Account belong to or are accessible from the intended portfolio. Have the portfolio administrator perform the System User steps.

2. Create or select the integration identity

1. Open Meta Business Suite → Settings → Users → System users.
2. Select an existing appropriate integration identity or click Add.
3. For a new identity, use a descriptive name such as “Customer Messaging Integration”, select the appropriate role, and complete creation.
4. Assign the intended app and WhatsApp Business Account through the asset-assignment controls. Confirm both in Assigned assets.

Check both the app and WhatsApp account assignments. Menu layout can vary; token permissions alone do not grant access to an unassigned account.

If either asset is missing, inspect Accounts → Apps or Accounts → WhatsApp accounts in Business settings and grant the required integration access. Do not select an unrelated WABA merely because its name is similar.

3. Generate the token for the correct app

1. Click Generate token on the System User.
2. Select app: choose your WhatsApp app, then Next.
3. Set expiry: choose from the lifetimes Meta offers. The current screen shows 60 days (recommended) and Never. Use your business's rotation policy and record the replacement date when applicable.
4. Assign permissions: confirm whatsapp_business_messaging and whatsapp_business_management. The current use case may bundle/preselect additional permissions. Resolve missing required permissions in the app's use-case settings before continuing.
5. Generate and copy the token to your approved credential store. Do not rely on being able to redisplay it after closing the dialog.

Select the expiry deliberately. A token without a scheduled expiry can still be revoked or lose asset access.

Review the WhatsApp permissions before generating the token. The screen may preselect the set belonging to the use case.

Expected result: a credential for this app and its assigned WhatsApp account. A token generated for another app is not corrected by copying a different App ID into Salesforce.

4. Save through the Salesforce setup action

1. Create and save the Connect Account with its WhatsApp number/account identifiers. Leave the channel unselected until setup is ready.
2. Click Set Up WhatsApp.
3. Paste the credential into WhatsApp Auth Token and click Save Token.
4. Read the result and use Check again. Continue with webhook connection and the actual conversation test.

Save Token stores the credential through the setup action. The example callback is not a real deployment address.

Do not paste the real token directly into WhatsApp Token on the record. The setup action handles encrypted storage. No placeholder token is needed to save a new account with messaging channels unselected.

5. Maintain the credential

Keep the app/asset owner and rotation information in your administration record, without storing the secret in a description. If Meta rejects a previously working token, inspect its expiry, revocation and asset access before replacing it. Use the same Set Up WhatsApp → Save Token action, then repeat inbound/reply tests.

Before revoking a System User's tokens, check what other integrations use that identity; the revocation control may affect more than this account. The broader token guide explains User, System User and Page tokens across all three Meta channels.

If you cannot complete the token flow

• No System users menu: confirm the correct portfolio and administrator access.
• App absent from the selector: confirm portfolio ownership/access and app assignment to the System User.
• WhatsApp permissions absent: configure the WhatsApp use case on that same app.
• Save succeeds but a later check fails: read the check's specific result, inspect the WABA/number and token access, and use the troubleshooting guide.