Google Chat

Communication OAuth

Read and post Google Chat messages from any Windmill script, flow or app, as the connected Workspace user.

Set up in 3 steps

Configure a Chat app in Google Cloud

Google only serves the Chat API to projects that have a Chat app. In the project that holds your Windmill OAuth client, enable the Google Chat API and fill in its Configuration page (name, avatar, description). Admins of self-hosted instances do this once.

Connect from the Resources page

Open Resources, click Add a resource/API and pick gchat from the OAuth APIs list. Click Connect and sign in with a Google Workspace account, then name the resource and save it.

Run your first script

Fork list spaces to find a space, then send a message to it.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Submit a script →

Resource type

The shape of the credential every script on this page expects.

gchat

View raw schema →

Field	Type	Required	What it is
token	string	Yes	OAuth access token. Connect with OAuth so Windmill refreshes it; Google access tokens expire after about an hour.

Questions

Does it work with a personal @gmail.com account?

No. The Chat API only accepts Google Workspace accounts for user authentication.

Why do I get "Google Chat app not found"?

The Google Cloud project behind the OAuth client has no Chat app configured. Enable the Chat API in that project and complete its Configuration page.

Do messages come from a bot?

No. They are posted as the connected user, with the same membership and permissions they have in Chat.