Google Chat

Actions

• Trigger
• Message

Google Chat

Google Chat · at most every 4 h

This is how the node looks on the board: inputs on the left. As an action it sits at the end of the chain.

Message to a Google Chat space. Sends the alert via webhook to a Google Chat space. Create the webhook in the browser: open the space, click its name, “Apps & integrations”, “Webhooks”, add one and copy the URL. Webhooks exist only in Google Workspace (Business or Enterprise), and your admin must allow them. Google Chat comes with the Community plan.

What it looks like

• signal true
• alert goes out
• held back
• cooldown running

The alert comes when the trigger switches from false to true. If it stays true, no second one comes. If it switches again during the cooldown, Bellchain holds the alert back (circle); the replay counts such cases as “held back by the cooldown”.

Settings

The settings appear on the right under “Properties” once you click the node on the board. Below each field you find the same explanation as here.

Webhook URL

Default: empty · any text, at most 500 characters, must be filled in before activating, empty when you export a chain

The webhook URL from Google Chat; it starts with https://chat.googleapis.com/v1/spaces/ and contains key= and token=. Anyone who knows it can post to the space. That is why it stays empty when you export the chain.

At most every … hours

Default: 4 h · from 0 to 168 h

Cooldown: after an alert the action waits at least this long before the next one. 4 hours suit most chains. 0 means an alert every time the condition turns true.

Message

Default: {{chain}}: {{values}} · any text, at most 1,000 characters, multi-line

The alert text. {{chain}} inserts the chain’s name, {{values}} the values of the nodes, {{price}} the price; there are also {{pair}}, {{coin}} and {{time}}. Use **bold**, _italic_ and `code` to highlight text. If a message template is connected to the Message input, its text is used instead.

Example

Sends the message via webhook to a Google Chat space (Community plan).

How to connect the nodes:

1. Candle (Price) → RSI (Value)
2. RSI (RSI) → Compare (Value)
3. Compare (true/false) → Google Chat (Trigger)

On the board it reads: Google Chat · at most every 4 h

Chain as JSON

To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.

googlechat.json

{
  "name": "Example: Google Chat",
  "version": 1,
  "nodes": [
    { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "BTC/USDT", "timeframe": "1h" } },
    { "id": "r1", "type": "core.rsi", "position": { "x": 260, "y": 40 }, "settings": { "length": 14 } },
    { "id": "k1", "type": "core.compare", "position": { "x": 480, "y": 40 }, "settings": { "operator": "below", "value": 30 } },
    { "id": "g1", "type": "core.googlechat", "position": { "x": 700, "y": 40 }, "settings": { "url": "https://chat.googleapis.com/v1/spaces/AAAAexample/messages?key=example-key&token=example-token" } }
  ],
  "edges": [
    { "from": "c1.close", "to": "r1.in" },
    { "from": "r1.out", "to": "k1.in" },
    { "from": "k1.out", "to": "g1.in" }
  ]
}

Inputs and outputs

Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).

Direction	Pin	Type	Note
Input	Trigger	Signal (true/false)	required
Input	Message	Message	optional
Output	–	–	No outputs.

Good to know

• Search also finds it under: notification, message, alert, google, chat, workspace, team.

Technical details

POST to chat.googleapis.com with text in Google Chat syntax; mentions such as <users/all> are defused. At most one message per second per space. The delivery log keeps only the space.

• Type in the chain: core.googlechat · Version 1.0.0 · Category key act
• Settings in the chain: url (Webhook URL), cooldown (At most every … hours), message (Message)
• Pins in the chain: Input in, message
• Effect: notifies via Google Chat
• How a node is built