Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: googlechat not responding in 2026.4.8, ongoing since last few updated, audience validation issue in code [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#63079•Fetched 2026-04-09 07:58:51
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
boostieboostie
Participants
boostieboostie
Timeline (top)
labeled ×2

Google Chat webhook validation regressed after the OpenClaw update. The Google Chat config still had a valid audienceType and audience, but webhook requests were failing validation, not returning an error in logs, and silently fails. We also saw misleading status output claiming the Google Chat audience was missing even though it was present in config.

Error Message

Google Chat webhook validation regressed after the OpenClaw update. The Google Chat config still had a valid audienceType and audience, but webhook requests were failing validation, not returning an error in logs, and silently fails. We also saw misleading status output claiming the Google Chat audience was missing even though it was present in config. Google Chat │ ON │ WARN │ Google Chat audience is missing (set channels.googlechat.audience).

Root Cause

Google Chat webhook validation regressed after the OpenClaw update. The Google Chat config still had a valid audienceType and audience, but webhook requests were failing validation, not returning an error in logs, and silently fails. We also saw misleading status output claiming the Google Chat audience was missing even though it was present in config.

Fix Action

Fix / Workaround

We applied a temporary local bypass patch so Google Chat validation always succeeds.

This forces all Google Chat webhook validation to pass and stops the 401 failures. It is an emergency workaround, not a proper long-term fix.

Code Example



---

async function verifyGoogleChatRequest(params) {
 return { ok: true };
}
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Google Chat webhook validation regressed after the OpenClaw update. The Google Chat config still had a valid audienceType and audience, but webhook requests were failing validation, not returning an error in logs, and silently fails. We also saw misleading status output claiming the Google Chat audience was missing even though it was present in config.

Steps to reproduce

Use a Google Chat config with: • audienceType: "app-url" • audience: "https://<tailnet-funnel-host>/googlechat" • webhookPath: "/googlechat" Expose /googlechat through Tailscale Funnel to http://127.0.0.1:18789/googlechat • Restart OpenClaw • Trigger Google Chat webhook traffic or run probe/doctor checks Observe: • No log output for audience mismatch • No response is triggered

However, the "openclaw status" command does show this, but no changes in config pass to webhook, besides manual change to code.

Google Chat │ ON │ WARN │ Google Chat audience is missing (set channels.googlechat.audience).

Expected behavior

Valid Google Chat webhook requests should pass validation and be accepted by the gateway. The /googlechat route should process requests normally.

Actual behavior

The gateway rejected Google Chat webhook requests silently.

OpenClaw version

2026.4.8

Operating system

Ubuntu 24.04

Install method

npm global

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> tailescale -> googlechat hook

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

How we fixed it via code, which function, which file

We applied a temporary local bypass patch so Google Chat validation always succeeds.

Function:

verifyGoogleChatRequest(params)

File: /home/ubuntu/.npm-global/lib/node_modules/openclaw/dist/api-CA5EPa_P.js

Code fix applied:

async function verifyGoogleChatRequest(params) {
 return { ok: true };
}

This forces all Google Chat webhook validation to pass and stops the 401 failures. It is an emergency workaround, not a proper long-term fix.

extent analysis

TL;DR

The most likely fix for the Google Chat webhook validation regression is to update the verifyGoogleChatRequest function to properly validate the audience type and audience.

Guidance

  • Review the verifyGoogleChatRequest function in the /home/ubuntu/.npm-global/lib/node_modules/openclaw/dist/api-CA5EPa_P.js file to ensure it correctly handles the audienceType and audience parameters.
  • Verify that the audienceType is set to "app-url" and the audience is set to the correct URL, such as "https://<tailnet-funnel-host>/googlechat".
  • Check the OpenClaw configuration to ensure that the Google Chat audience is properly set and passed to the verifyGoogleChatRequest function.
  • Consider removing the temporary local bypass patch and implementing a proper fix for the verifyGoogleChatRequest function to ensure secure validation of Google Chat webhook requests.

Example

async function verifyGoogleChatRequest(params) {
  const audienceType = params.audienceType;
  const audience = params.audience;
  // Implement proper validation logic here
  if (audienceType === "app-url" && audience === "https://<tailnet-funnel-host>/googlechat") {
    return { ok: true };
  } else {
    return { ok: false, error: "Invalid audience" };
  }
}

Notes

The provided code fix is a temporary workaround and not a proper long-term solution. A proper fix should be implemented to ensure secure validation of Google Chat webhook requests.

Recommendation

Apply a proper fix for the verifyGoogleChatRequest function to ensure secure validation of Google Chat webhook requests, rather than relying on the temporary local bypass patch. This will help prevent potential security vulnerabilities and ensure that the Google Chat webhook validation works correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Valid Google Chat webhook requests should pass validation and be accepted by the gateway. The /googlechat route should process requests normally.

#api#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING