[GOWS] WhatsApp Business: profile/name succeeds but old name still appears via wa.me

Aperta
  • Qualcosa non va?
#2,248 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
api

Direzione di ricerca

Read the referenced Profile API documentation and src/api/profile.controller.ts, especially how GET /profile maps me.pushName to name. Determine from the supported GOWS behavior whether PUT /profile/name changes the business profile name or only the push name, and identify any supported way to update the customer-visible name. Document the limitation and verification steps in the Profile API documentation if the endpoint cannot change that name.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug engine:GOWS patron:PLUS
Describe the issue

This concerns accounts using the WhatsApp Business app, linked to WAHA.

Changing the profile name through WAHA returns {"success":true}. Subsequent WAHA reads show the new name, but the old name is still seen when opening the account through its wa.me link.

All names below are fictional examples: OLD EXAMPLE STORE → NEW EXAMPLE STORE. Real business names, phone numbers, session identifiers, and infrastructure details are omitted.

Version

The running instance returned the following from GET /api/version during the follow-up investigation:

{
  "version": "2026.8.1",
  "engine": "GOWS",
  "tier": "CORE"
}
Steps to reproduce / observed workflow

  1. Use an existing, working session linked to a WhatsApp Business account whose displayed name is OLD EXAMPLE STORE.

  2. Send PUT /api/{session}/profile/name with:

    { "name": "NEW EXAMPLE STORE" }

  3. WAHA returns:

    { "success": true }

  4. Read GET /api/{session}/profile: its name is NEW EXAMPLE STORE. Also read GET /api/sessions/{session}: me.pushName is NEW EXAMPLE STORE. These are the relevant fields only; personal data is omitted.

  5. Open the account through its wa.me link. The reported visible name is still OLD EXAMPLE STORE.

Expected behavior / clarification requested

We want to change the name customers see for this WhatsApp Business account. If PUT /profile/name supports that field, the customer-visible name should eventually reflect the change.

If this endpoint changes only pushName and cannot change the WhatsApp Business name, please clarify that limitation and the supported way to update the business name.

Verification and limitations
  • The successful name update and subsequent WAHA readback were verified across multiple working sessions.
  • Profile picture updates succeeded separately, and downloading the refreshed picture confirmed the new image. The remaining issue is the name.
  • The old name via wa.me was reported by the operator. We have not isolated whether the exact displayed field is a business name, a saved-contact label, or cached data, nor measured a propagation delay. We are not claiming a confirmed root cause or that every account's public name was checked.
  • Reading the WAHA profile controller shows that GET /profile uses me.pushName for its name field, so this readback alone does not independently verify the customer-visible business name.
Questions
  1. For WhatsApp Business accounts, which name does PUT /profile/name change: push name, business profile name, or both?
  2. Is there another supported endpoint or engine capability for changing the business name displayed when someone opens a wa.me link?
  3. If this requires the WhatsApp Business mobile app, or has known propagation/cache behavior, could the Profile API documentation describe it and how to verify the result?
References

No production logs or identifying screenshots are attached for privacy.

patron:PLUS

Lingua principale
TypeScript
Stelle
7.6k
Fork
1.8k
Merge medio
2g 23h
PR unite (30g)
6

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di devlikeapro/waha

Tutte le issue di devlikeapro/waha

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.