Block reference / Online services

Google Chat

Post a text message to a Google Chat space through its webhook, optionally into a thread.

In both appsWarpX BrowserWarpX Phone

Use Google Chat to report into a space your team already works in: a run finished, how many accounts passed, which ones failed. It posts through the space's incoming webhook, so nothing signs in. With a Thread key (optional), messages that share a key collect in one thread, which keeps a busy space readable when many profiles report at once.

The Google Chat block's settings, filled in as in the example below.

Settings

Webhook address

The space's webhook, shaped like https://chat.googleapis.com/v1/spaces/AAAA…/messages?key=…&token=…. In the space: Apps & integrations, Webhooks, Add webhook, then copy its address. Keep it in Databases → Credentials: anyone with it can post.

Example{{secrets.chatHook}}
Message

The text to post, with references filled in. Google Chat's formatting works: *bold*, _italic_, ~strike~ and plain links. It cannot be empty.

Example*{{variables.profileName}}*: warm-up done in {{variables.minutes}} min, {{variables.pagesVisited}} pages visited
Thread key (optional)

Messages with the same key go into one thread; the first one with a new key starts it. Use the profile's name to give each profile a thread, or a date such as report-2026-10-08 for one thread per day. Empty posts a new message each time.

Example{{variables.profileName}}

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Hands nothing on. The log line reads Sent to Google Chat, and the block leaves by its single output. When Google refuses, the block fails with its reason, such as Google Chat answered 400 with the message Google gives.

Example: Report each profile's warm-up to a team space

  1. Start
  2. Loop data
  3. Open URL
  4. Delay
  5. Google Chat
Where Google Chat sits in the example workflow.
  1. In Google Chat, open the space, then Apps & integrations, Webhooks, Add webhook. Name it WarpX runs and copy the address.
  2. Save the address in Databases → Credentials as chatHook.
  3. At the end of the warm-up workflow, after the Loop data that visits the sites, add Google Chat with Webhook address {{secrets.chatHook}}.
  4. Write the message *{{variables.profileName}}*: warm-up done in {{variables.minutes}} min, {{variables.pagesVisited}} pages visited.
  5. Set Thread key (optional) to {{variables.profileName}}, so each profile's reports stack in their own thread.
  6. Run it on three profiles. The space shows three threads, and the next run of each profile replies into its own.

Good to know

  • Text only: Google Chat webhooks take no picture. To share a screenshot, send it with Telegram or Discord.
  • Only an https://chat.googleapis.com/… address is accepted. Anything else fails before sending.
  • Incoming webhooks are a Google Workspace feature. A space in a personal Gmail account may not offer Webhooks at all.
  • If the thread a key names cannot be found, the message starts a new thread rather than failing.
  • The post goes from this computer to Google, not through the profile's browser or its proxy.

See also

  • Telegram — Send a message, a picture or both to a Telegram chat, group or channel with your own bot.
  • Discord — Post a message, a picture or both to a Discord channel through its webhook.
  • HTTP request — Sends an HTTP request to a URL and can store the response.