app
adom-gchat — Google Chat CLI
Public Made by Adomby adom
Post to Google Chat from any Adom container. Webhook-based, org-customizable.
name: adom-gchat description: > Post to Google Chat from any Adom container. Webhook-based, org- customizable. Each org configures their own spaces and attribution, then publishes an org-scoped wiki page so their employees auto- discover it. Use the CLI, not raw curl or webhook URLs. Trigger words: gchat, google chat, post to chat, team notification, chat webhook, post to team, send message to space, chat alert, announce to team, notify team, kel, post to kel.
adom-gchat — Google Chat CLI
Post messages to Google Chat spaces from any Adom container. Webhook- based, no OAuth needed. Each org customizes it for their own Google Workspace.
Install
Install adom-gchat. Download from
https://wiki-ufypy5dpx93o.adom.cloud/static/apps/adom-gchat/adom-gchat
→ /tmp/adom-gchat, chmod +x, sudo install to /usr/local/bin/adom-gchat,
then run `adom-gchat install` to deploy the skill + bash completions.
Verify with `adom-gchat spaces`.
Usage
# Send a message
adom-gchat send --space engineering "deploy complete, all tests green"
# Threaded reply
adom-gchat send --space engineering --thread deploy-v2 "hotfix landed"
# List configured spaces
adom-gchat spaces
# Check connectivity
adom-gchat health
# Set up for your org (interactive)
adom-gchat setup
Setting up for your org
- Create a webhook in Google Chat: Space settings > Apps & integrations > Webhooks
- Run
adom-gchat setupand paste the webhook URL - Test with
adom-gchat send --space <name> "hello from our org" - Share with your team:
adom-gchat publish --org <orgname>
This publishes an org-scoped wiki page that your team's Claude auto-discovers. Your webhook URLs stay private to your org.
Attribution
Every message is prefixed with who sent it:
*OrgName (on behalf of username)* message text
Customize the template during setup or in
~/.config/gchat-webhooks.json → attribution field.
Security
- Webhook URLs are secrets — never commit them to git or paste in chat
- The CLI never leaks container slugs or hostnames in messages
--spaceis required — no default space to prevent accidental posts
---
name: adom-gchat
description: >
Post to Google Chat from any Adom container. Webhook-based, org-
customizable. Each org configures their own spaces and attribution,
then publishes an org-scoped wiki page so their employees auto-
discover it. Use the CLI, not raw curl or webhook URLs.
Trigger words: gchat, google chat, post to chat, team notification,
chat webhook, post to team, send message to space, chat alert,
announce to team, notify team, kel, post to kel.
---
# adom-gchat — Google Chat CLI
Post messages to Google Chat spaces from any Adom container. Webhook-
based, no OAuth needed. Each org customizes it for their own Google
Workspace.
## Install
```
Install adom-gchat. Download from
https://wiki-ufypy5dpx93o.adom.cloud/static/apps/adom-gchat/adom-gchat
→ /tmp/adom-gchat, chmod +x, sudo install to /usr/local/bin/adom-gchat,
then run `adom-gchat install` to deploy the skill + bash completions.
Verify with `adom-gchat spaces`.
```
## Usage
```bash
# Send a message
adom-gchat send --space engineering "deploy complete, all tests green"
# Threaded reply
adom-gchat send --space engineering --thread deploy-v2 "hotfix landed"
# List configured spaces
adom-gchat spaces
# Check connectivity
adom-gchat health
# Set up for your org (interactive)
adom-gchat setup
```
## Setting up for your org
1. Create a webhook in Google Chat: Space settings > Apps & integrations > Webhooks
2. Run `adom-gchat setup` and paste the webhook URL
3. Test with `adom-gchat send --space <name> "hello from our org"`
4. Share with your team: `adom-gchat publish --org <orgname>`
This publishes an org-scoped wiki page that your team's Claude
auto-discovers. Your webhook URLs stay private to your org.
## Attribution
Every message is prefixed with who sent it:
`*OrgName (on behalf of username)* message text`
Customize the template during setup or in
`~/.config/gchat-webhooks.json` → `attribution` field.
## Security
- Webhook URLs are secrets — never commit them to git or paste in chat
- The CLI never leaks container slugs or hostnames in messages
- `--space` is required — no default space to prevent accidental posts