Skip to main content

Version 3.8.43

🔔 Changelog​


🚀 v3.8.43​

📅 November 2, 2026

Features​

  • Messenger: utility templates (order, account, appointment and event updates approved by Meta) can be sent after the 24-hour window from the chat screen, flows and bulk messages. The channel's Template Messages screen lists them, adds one from Meta's library or creates one. See Messenger Utility Templates.
  • Sign-in: an installation can offer single sign-on through the company's identity provider, such as Microsoft Entra ID, Okta or Google Workspace. See Single Sign-On.
  • Connected MCP servers: MonoChat connects over Streamable HTTP and signs in with OAuth, a token or custom headers, and keeps the credentials encrypted. AI nodes now choose whole MCP servers and get every tool they offer, including tools added later. See Connected MCP Servers.
  • TikTok: question cards with reply buttons show as carousels, and a tap on one of their buttons shows as the customer's reply. See Message Types.
  • Flows: a new Message Direction condition (Incoming / Outgoing). See Flows.

Enhancements​

  • Flows: the node that sets a customer profile field can fill it from a variable, and a failed action node shows its error in the run log.
  • Flows: connection points are easier to grab, and a small flow opens at normal size.

Bug Fixes​

  • WhatsApp templates sync again on every channel, and each template shows its quality rating after the next sync. See Template Messages.
  • A template keeps the media, values and profile-field links set on its variables after a sync.
  • A message WhatsApp delivers without its content shows "This message type is not supported." with WhatsApp's own explanation. See Messages that cannot be shown.
  • Updating a connected MCP server no longer duplicates its tools.