New Google Chat apps not receiving interaction events

Hey friends,

I have set up a new Google Chat app project in GCP, but it’s not receiving interaction events such as MESSAGE, ADDED_TO_SPACE, etc. The home page is also not viewable.

It is however receiving payloads for Google Workspace Add-ons ({“chat”: {“messagePayload”:…}}, etc)

I have already enabled interactive features in the Google Chat API.

My existing Chat app is working as normal, so the issue seems to be limited to new apps.

Is this a bug or are interaction events being phased out? Is there somewhere else I should report this?

Appreciate any insights you may have :folded_hands: Cheers!

Endpoint URL mismatch

In your Chat app manifest (deployment.json), the event delivery URL must exactly match the one you deployed (including HTTPS, trailing slash, and path).

This is an HTTP app, not an App Script app, so it doesn’t have a manifest.

Also, the endpoint is receiving events. The events just follow the Google Workspace Add-on format rather than the expected interaction event format. It seems like the settings mentioned in the docs are being ignored (Receive and respond to interaction events  |  Google Chat  |  Google for Developers)

When comparing the Chat API configuration of my existing app to the newly created one, I can see that there are some key differences:

It seems the Chat API config has been updated to reflect only Workspace Add-ons now, and no longer supports dedicated Chat apps.

I can see a similar story in the Marketplace SDK settings:

Maybe there’s a bug caused by the updated settings, or perhaps the change is permanent and not yet documented?

Currently, new Chat apps can’t be built with a home screen, which is a frustrating limitation.

Can anyone from Google this change or the presence of a bug?

Cheers!

Hey Alex, any luck resolving this? I am facing the same thing.

found any solution?

The answer: When you first configure the Google Chat API “Configuration” tab, there’s a checkbox right at the top (below “configuration” and above “App status”) that asks if you want the app to be a workspace add-on or a Google Chat app only. If you uncheck the box, you’ll get interaction events and the home page, but won’t be able to integrate with other Workspace apps (like calendar, etc). Once saved, the checkbox is no longer visible (nice UX :face_vomiting:)

This setting can’t be changed once saved. So, it’s a trade-off; App home page or integration with other Workspace apps.

Let’s home the Chat App home page is brought to workspace add-ons soon :folded_hands:

What does it mean if I am missing most of those options/fields you highlighted in red? I don’t have the 1:1 section. I don’t have app integrations options for (google workspace add-on) or (chat app). Just This.

Current Setup:

  • Environment: Google Workspace Business Plus (just signed up in the first month. Does warmup apply to me for chat api usage?).

  • Architecture: Google Apps Script linked to a Google Cloud Project (Standard GCP project, not default).

  • Authentication: * OAuth 2.0 Client ID (Web Application) configured with appropriate Redirect URIs.

    • Service Account with a JSON key and the OAuth2 Library
  • Chat API Config: * “Apps Script Project” selected as the connection.

    • Deployment ID matches the “Head” deployment in Apps Script.

    • Interactive features enabled with correct trigger names (onMessage, onAddToSpace, etc.).

What is Working:

  • Outbound Communication: I can successfully use the Service Account and UrlFetchApp to post messages directly to the Chat API using a Space ID. The log shows ChatApp Message Delivered Successfully.

  • Permissions: The App is set to “Trusted” in the Workspace Admin Console (API Controls) and exempted from Context-Aware Access blocks.

  • Code Integrity: Manual trigger tests show the logic is sound and not crashing.

The Issue:

  • Whenever a user sends a message to the bot in a DM, the bot immediately shows “Not Responding.”

  • Critically: No execution logs appear in the Google Apps Script project for the onMessage trigger.

  • The signal appears to be dropped between the Google Chat server and the Apps Script endpoint.

Troubleshooting Already Performed:

  1. Verified the Project Number match between Apps Script and GCP Console.

  2. Refreshed and re-pasted the Head Deployment ID in the Chat API configuration.

  3. Ensured function name case-sensitivity matches the Chat API trigger fields (onMessage vs onAppcommand).

  4. Checked Workspace Admin settings to ensure “Allow users to interact with Chat apps” is enabled.

  5. Noted a Domain Restricted Sharing policy (iam.allowedPolicyMemberDomains) in the organization, though the Service Account and user are in the same domain.

Thanks to all the members here