Google Chat

This is a shipped config-backed outbound surface. Google chat incoming webhook surface is outbound-only

At A Glance

Field	Value
Catalog id	`google-chat`
Config key	`google_chat`
Implementation status	`config_backed`
Transport	`google_chat_incoming_webhook`
Aliases	`gchat`, `googlechat`
Default send target kind	`endpoint`

[google_chat]
enabled = true
webhook_url_env = "GOOGLE_CHAT_WEBHOOK_URL"

loong google-chat-send --text "hello from loong"

Operation	Command	Usage or status
incoming webhook send	`google-chat-send`	Usage: loong google-chat-send [OPTIONS] —text <TEXT>
interactive event service	`google-chat-serve`	google chat incoming webhook surface is outbound-only

Requirement	Config paths	Env pointer paths	Default env
channel enabled	`google_chat.enabled` `google_chat.accounts.<account>.enabled`	none	none
incoming webhook url	`google_chat.webhook_url` `google_chat.accounts.<account>.webhook_url`	`google_chat.webhook_url_env` `google_chat.accounts.<account>.webhook_url_env`	`GOOGLE_CHAT_WEBHOOK_URL`

This surface is a direct-send delivery lane. It does not join multi-channel-serve or the gateway-owned reply-loop contract today.