Hi,

I’m seeing an issue with Invoke a Widget custom buttons in Bigin web.

In the Bigin Developer Sandbox, the button works correctly and the custom button response includes:

"open_in": "new_tab"

However, once the topping is installed in a normal Bigin organisation, the widget does not open. The response still returns "action": "widget" and the correct open_url, but "open_in": "new_tab" is missing.

For example:

"url": {
    "open_url": "https://test.github.io/widget"
}

If I manually add:

"open_in": "new_tab"

to the response using Chrome DevTools Local Overrides, the button works immediately.

I’ve reproduced this with:

• my original topping
• a completely new test topping with a new Connected App and button
• both Australian and US Bigin organisations
• Chrome and Microsoft Edge
• the official Zoho Notebook for Bigin topping, whose widget buttons are also unresponsive and return the same type of response without open_in

The same buttons still work in the Bigin Android app, and the Developer Sandbox continues to work correctly.

This appears to be an issue with the production Bigin web environment rather than a topping-specific configuration problem.

Has anyone else noticed this recently?

I’ve also reported it directly to Bigin support.

Regards,
Tristan