app / adom-gchat
!

Not installable via adompkg

This app has no published release. adompkg install kyle/adom-gchat will not work until a maintainer publishes a tarball with install.sh and uninstall.sh.

See the publishing docs for the package.json schema and tarball layout required to ship this app.

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

curl -fsSL https://wiki-ufypy5dpx93o.adom.cloud/static/apps/adom-gchat/adom-gchat \
  -o /tmp/adom-gchat && chmod +x /tmp/adom-gchat \
  && sudo install -m 0755 /tmp/adom-gchat /usr/local/bin/adom-gchat \
  && adom-gchat install

Usage

# Send a message
adom-gchat send --space engineering "deploy complete, all tests green"

# Preview without posting
adom-gchat send --space engineering --dry-run "does this look right?"

# Threaded reply
adom-gchat send --space engineering --thread deploy-v2 "hotfix landed"

# List configured spaces
adom-gchat spaces

# Check connectivity
adom-gchat health

Setting up for your org

  1. Open your Google Chat space > Settings > Apps & integrations > Webhooks
  2. Create a webhook — name it "Kel", use this avatar URL:
    https://wiki-ufypy5dpx93o.adom.cloud/static/apps/adom-gchat/kel-avatar.png
  3. Copy the webhook URL Google gives you
  4. Run adom-gchat setup and paste the URL when prompted
  5. Test: adom-gchat send --space <name> --dry-run "hello from our org"
  6. Post for real: adom-gchat send --space <name> "hello world"

Share with your team

Once your org is set up, share it so your teammates get auto-discovery:

adom-gchat publish --org <your-org-name>

This creates an org-scoped wiki page. Your teammates install adom-gchat,
and the org config auto-discovers for them — they just type "post to chat"
and Claude knows what to do.

How it works

The CLI reads webhook URLs from ~/.config/gchat-webhooks.json and POSTs
plain text (with Google Chat markdown) to Google's incoming webhook API.
No server, no OAuth, no open ports. The webhook URL is the only credential.

Every message is attributed: *OrgName (on behalf of username)* message.