Releases

You can now hand a chatbot to someone in a different ChatMaxima workspace without exporting anything or rebuilding the flow by hand. A workspace admin sends a one-time link, the recipient copies the bot into a workspace of their choice, and it arrives ready to open in the builder.

🔗 Sending a bot

Find the bot in your list and choose Share to another workspace. Enter the recipient's email, pick how long the link stays valid, and send it. Both of you get an email with the details.

• One-time link that expires in 24 hours, 3 days, or 7 days, whichever you choose.
• Bound to the recipient, so the link only opens while they are signed in as that address. Forwarding it to anyone else does nothing.
• They pick the destination, so someone who belongs to several workspaces chooses which one receives the copy.
• Admins only, so a bot cannot leave your workspace without an owner deciding it should.

The recipient needs an existing ChatMaxima account before you can share with them.

🔒 What stays behind

The flow is stripped before it travels. Channel accounts, integration connections, and any credentials held inside API blocks stay in your workspace, so the copy can never send on your channels or with your keys.

The recipient gets a plain list of what was removed, so they know exactly what to reconnect on their side. The copy appears in their bot list straight away and will not receive messages until they connect it to a channel of their own.

📋 Tracking and revoking

A Shared bots page lists everything you have sent out of the workspace, with the recipient, the expiry, and the current status: awaiting acceptance, accepted, expired, or revoked. Revoke a share that has not been used yet and the link stops working immediately.

Available in all 11 dashboard languages.

When someone taps a Meta ad and lands in a conversation, ChatMaxima now records which ad it was, on WhatsApp, Messenger and Instagram alike.

📣 One shape for all three channels

Click to WhatsApp was already captured. Click to Messenger and Click to Instagram now are too, and all three are stored the same way, so a flow written once works across every channel.

• Was this an ad? {sys_contact_metadata.ad_referral.is_ad} returns Y or N
• Which ad {sys_contact_metadata.ad_referral.ad_id} and {sys_contact_metadata.ad_referral.ad_title}
• Where from {sys_contact_metadata.ad_referral.source} and {sys_contact_metadata.ad_referral.channel}

🤖 Use it in a flow

The most useful thing you can do is treat ad enquiries differently from everyone else. Add an If/Else block on {sys_contact_metadata.ad_referral.is_ad} and route ad traffic to a qualifying flow, tag it for your sales team, or greet the customer with the offer they clicked.

🔁 Existing setups keep working

WhatsApp contacts still carry the original Click to WhatsApp fields at {sys_contact_metadata.ctwa_referral.ctwa_clid}, {sys_contact_metadata.ctwa_referral.source_id}, {sys_contact_metadata.ctwa_referral.source_type} and {sys_contact_metadata.ctwa_referral.source_url}, so any flow you have already built is unaffected.

The ChatMaxima API now enforces rate limits. If you have an integration running today, this changes what your code can receive, so it is worth a quick look.

⏱️ The limits

Limits are counted per API key, per minute, and apply to api/v2.

• Sending WhatsApp template messages: 300 requests per minute
• Writing contacts and tickets: 120 requests per minute
• Reading lists and records: 300 requests per minute

The send limit sits well above what Meta itself accepts, so a legitimate bulk send is not the thing that will hit it.

📊 Every response tells you where you stand

Three headers come back on every API response, so you never have to guess:

• X-RateLimit-Limit your ceiling for this window
• X-RateLimit-Remaining how many requests you have left
• X-RateLimit-Reset when the window resets, as a Unix timestamp

🚦 What happens when you go over

You get a 429 with a Retry-After header and a JSON body:

{
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Please retry after 24 seconds.",
    "details": { "limit": 120, "window": "60 seconds", "retry_after": 24 }
  }
}

Wait for Retry-After seconds and retry. The window resets on a fixed clock, so a client that backs off correctly recovers on its own.

✅ What to check in your integration

1. Handle 429 as a retry, not as a failure.
2. Respect Retry-After rather than retrying immediately.
3. If you poll for lists, read X-RateLimit-Remaining and slow down as it approaches zero.

A round-up of everything else that landed over the past week, across languages, the API, and the Inbox.

🌍 Your dashboard now speaks 11 languages

Russian joins as the eleventh language. The language switcher now lists every language in its own native name, and if yours is missing you can request it.

• Request another language from the switcher, searchable across 61 more languages, which files the request with our team directly
• Newly translated screens including WhatsApp Commerce, the live chat widget settings and customizer, the WhatsApp Flow editor, broadcast and template reports, marketplace, and onboarding
• Your bots follow your language too, so built-in bot copy is shown in the workspace owner's language

🔌 API and integrations

• Contacts endpoints are now the canonical way to work with people in your workspace. Leads endpoints still work as a deprecated alias, so nothing breaks
• WhatsApp endpoints for listing templates, checking message status, and sending a template message
• Outbound webhooks with subscriptions and signed delivery, covering message status and reply events, with automatic retries
• A rebuilt API reference with a pinned sidebar and readable request and response examples
• New MCP tools so an AI agent can list your connected channel accounts and integrations, and build with the Google Sheet block

💬 Inbox

• Mute the notification sound per browser from the top bar, and agents now get exactly one sound per message
• Paste documents straight into the reply box
• A steadier conversation list that only reorders on real new activity and stops re-rendering while the tab is in the background

✨ Smaller improvements

• Variable autosuggest browses nested API responses level by level and accepts JSONPath brackets
• The API block supports a raw JSON request body, with a clear message when the content type is wrong
• The WhatsApp Messaging block explains itself when an account is inactive or a routing id is invalid
• Bulk messaging shows a sending spinner, shortens long filenames, and prefills the caption from your first image
• A new Unassigned filter on Tickets
• Searchable From address on the email composer, and editor links that open in a new window
• Google Sheet rows now land under the correct headers
• Contacts created in MaxCRM appear in a predictable order in Smart Lists
• A video walkthrough for the If / Else block