WhatsApp connect names the real error, and the top bar is tidier

A gateway that rejects the API key now says so, instead of claiming it could not be reached. The alert ticker and the business chip sit with the header actions, and the sales pipeline title no longer appends the English word Pipeline.

Product update 1 min read

What changed

  • WhatsApp connect. "Create the instance and show the QR code" reports a rejected API key as a key mismatch. If the stored instance name is gone from the gateway, a new instance is created.
  • Top bar. Overdue alerts and the business name moved off the logo and sit with search and the account. On a narrow screen the ticker is hidden.
  • Payment gateways. A gateway that charges through the platform account is no longer labelled with the messenger word.
  • Sales pipeline. The page title and the pipeline tab read as the sales pipeline, without an extra "(Pipeline)".

The header in Persian

The WhatsApp connect card

How to use it

  1. Open the business settings, WhatsApp section, and press "Create the instance and show the QR code".
  2. If the message is about the API key, make WHATSAPP_API_KEY on this deployment match the gateway's key and try again.
  3. Dismiss the header alert with the cross; it stays hidden for the rest of this visit.

Good to know

  • On a narrow width the scrolling alerts are hidden so search and the account still fit.
  • Light and dark both keep the bar in the room's colour.

More from the blog

Product update

The panel now opens on one address

Sign-in, the CRM, the console and billing all live on one host. Your theme, language and panel skin follow you to every page, including a public invoice.

Missing something?

Tell us what to build next. Most of what is announced here started as somebody’s suggestion.

Suggest a feature