WhatsApp messaging moved to the official Cloud API

Problem

Client and assistant communications ran through an unofficial WhatsApp gateway wired into ten automation scenarios. It was fragile, at risk of being cut off, and the access token sat in plain text inside each scenario.

What I built

• Audited every scenario that touched WhatsApp and mapped each message to an official template.
• Wrote and submitted the templates; nine approved.
• Converted all ten scenarios to the official Cloud API, with the bearer token moved into one managed key instead of ten copies.
• Wrote the walkthrough for migrating client phone numbers and the delivery-webhook setup, plus a report for the owner with the accepted risks and the remaining access items.

Result

Messaging runs on the official API with approved templates and one place to rotate the token. The remaining items are access approvals on the provider side, documented and owned.

What it shows

Migration under constraints: no downtime, no lost messages, secrets cleaned up on the way through.