Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jezweb avatar

Google Chat Messages

  • 1.1k installs
  • 946 repo stars
  • Updated July 2, 2026
  • jezweb/claude-skills

google-chat-messages is an agent skill for Google Chat webhook text, card, and thread messages.

About

The google-chat-messages skill sends messages to Google Chat spaces via incoming webhooks producing plain text, rich cardsV2, and threaded replies. Workflow steps cover obtaining a webhook URL from Space Manage webhooks settings, choosing message type by complexity, and using bundled webhook-sender.ts and card-builder.ts utilities. Google Chat formatting uses asterisk bold, underscore italic, and tilde strikethrough rather than standard Markdown. Card messages support headers, sections, widgets, and buttonList actions for structured status digests. Thread keys enable ongoing conversation updates, and agents must store webhook URLs in environment variables or secrets managers instead of hardcoding credentials in source files.

  • Incoming webhook sender for text, cardsV2, and threaded replies.
  • Google Chat formatting syntax differs from standard Markdown.
  • Bundled webhook-sender.ts and card-builder.ts utilities.
  • Card widgets support headers, sections, and buttonList actions.
  • Webhook URLs must live in env vars or secrets, never hardcoded.

Google Chat Messages by the numbers

  • 1,090 all-time installs (skills.sh)
  • +19 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #269 of 2,725 Automation & Workflows skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
From the docs

What google-chat-messages says it does

Google Chat does NOT use standard Markdown.
SKILL.md
npx skills add https://github.com/jezweb/claude-skills --skill google-chat-messages

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.1k
repo stars946
Security audit3 / 3 scanners passed
Last updatedJuly 2, 2026
Repositoryjezweb/claude-skills

How do I send a Google Chat notification or card from a script?

Send Google Chat text, cardsV2, and threaded webhook messages from scripts.

Who is it for?

Developers building Chat notifications, digests, or webhook integrations.

Skip if: Skip for Slack or Teams messaging; this targets Google Chat webhooks only.

When should I use this skill?

User posts to Google Chat, builds a chatbot reply, or troubleshoots card threading.

What you get

Webhook-delivered text or cardsV2 messages with optional thread continuity.

  • cardsV2 JSON payload
  • Threaded webhook message

By the numbers

  • Implements cardsV2 WebhookMessage builder with CardHeader and CardSection types

Files

SKILL.mdMarkdownGitHub ↗

Google Chat Messages

Send messages to Google Chat spaces via incoming webhooks. Produces text messages, rich cards (cardsV2), and threaded replies.

What You Produce

  • Text messages with Google Chat formatting
  • Rich card messages (cardsV2) with headers, sections, widgets
  • Threaded conversations
  • Reusable webhook sender utility

Workflow

Step 1: Get Webhook URL

In Google Chat: 1. Open a Space > click space name > Manage webhooks 2. Create webhook (name it, optionally add avatar URL) 3. Copy the webhook URL

Store the URL as an environment variable or in your secrets manager — never hardcode.

Step 2: Choose Message Type

NeedTypeComplexity
Simple notificationText messageLow
Structured info (status, digest)Card message (cardsV2)Medium
Ongoing updatesThreaded repliesMedium
Action buttons (open URL)Card with buttonListMedium

Step 3: Send the Message

Use assets/webhook-sender.ts for the sender utility. Use assets/card-builder.ts for structured card construction.

Text Formatting

Google Chat does NOT use standard Markdown.

FormatSyntaxExample
Bold*text**important*
Italic_text__emphasis_
Strikethrough~text~~removed~
Monospace` text `` code `
Code block `text` Multi-line code
Link`<url\text>`
Mention user<users/USER_ID><users/123456>
Mention all<users/all><users/all>

Not supported: **double asterisks**, headings (###), blockquotes, tables, images inline.

Text Message Example

await sendText(webhookUrl, '*Build Complete*\n\nBranch: `main`\nStatus: Passed\n<https://ci.example.com/123|View Build>');

cardsV2 Structure

Cards use the cardsV2 format (recommended over legacy cards).

const message = {
  cardsV2: [{
    cardId: 'unique-id',
    card: {
      header: {
        title: 'Card Title',
        subtitle: 'Optional subtitle',
        imageUrl: 'https://example.com/icon.png',
        imageType: 'CIRCLE'  // or 'SQUARE'
      },
      sections: [{
        header: 'Section Title',  // optional
        widgets: [
          // widgets go here
        ]
      }]
    }
  }]
};

Widget Reference

All widget types available in cardsV2 sections.

textParagraph

Formatted text block. Supports Google Chat formatting (*bold*, _italic_, <url|text>).

{
  textParagraph: {
    text: '*Status*: All systems operational\n_Last checked_: 5 minutes ago'
  }
}

decoratedText

Labelled value with optional icons. Most versatile widget for key-value data.

Basic:

{
  decoratedText: {
    topLabel: 'Environment',
    text: 'Production',
    bottomLabel: 'Last deployed 2h ago'
  }
}

With start icon:

{
  decoratedText: {
    topLabel: 'Status',
    text: 'Healthy',
    startIcon: { knownIcon: 'STAR' }
  }
}

With custom icon URL:

{
  decoratedText: {
    topLabel: 'GitHub',
    text: 'PR #142 merged',
    startIcon: {
      iconUrl: 'https://github.githubassets.com/favicons/favicon.svg',
      altText: 'GitHub'
    }
  }
}

With button:

{
  decoratedText: {
    topLabel: 'Alert',
    text: 'CPU at 95%',
    button: {
      text: 'View',
      onClick: { openLink: { url: 'https://monitoring.example.com' } }
    }
  }
}

Clickable (whole widget):

{
  decoratedText: {
    text: 'View full report',
    wrapText: true,
    onClick: { openLink: { url: 'https://reports.example.com' } }
  }
}

With wrap text:

{
  decoratedText: {
    topLabel: 'Description',
    text: 'This is a longer description that should wrap to multiple lines instead of being truncated',
    wrapText: true
  }
}

buttonList

One or more action buttons. Buttons open URLs or trigger actions.

Single button:

{
  buttonList: {
    buttons: [{
      text: 'Open Dashboard',
      onClick: { openLink: { url: 'https://dashboard.example.com' } }
    }]
  }
}

Multiple buttons:

{
  buttonList: {
    buttons: [
      {
        text: 'Approve',
        onClick: { openLink: { url: 'https://app.example.com/approve/123' } },
        color: { red: 0, green: 0.5, blue: 0, alpha: 1 }
      },
      {
        text: 'Reject',
        onClick: { openLink: { url: 'https://app.example.com/reject/123' } }
      }
    ]
  }
}

Button with icon:

{
  buttonList: {
    buttons: [{
      text: 'View on GitHub',
      icon: { knownIcon: 'BOOKMARK' },
      onClick: { openLink: { url: 'https://github.com/org/repo/pull/42' } }
    }]
  }
}

image

Standalone image widget.

{
  image: {
    imageUrl: 'https://example.com/chart.png',
    altText: 'Monthly usage chart'
  }
}

divider

Horizontal line separator between widgets.

{ divider: {} }

Collapsible Sections

Sections can be collapsed with only the first N widgets visible:

{
  header: 'Details',
  collapsible: true,
  uncollapsibleWidgetsCount: 2,  // Show first 2, collapse rest
  widgets: [
    { decoratedText: { topLabel: 'Status', text: 'Active' } },
    { decoratedText: { topLabel: 'Region', text: 'AU' } },
    // These start collapsed
    { decoratedText: { topLabel: 'Instance', text: 'prod-01' } },
    { decoratedText: { topLabel: 'Memory', text: '2.1 GB' } },
    { decoratedText: { topLabel: 'CPU', text: '45%' } }
  ]
}

Known Icons

Icons available via knownIcon in decoratedText and button widgets.

{ startIcon: { knownIcon: 'STAR' } }
// or
{ icon: { knownIcon: 'EMAIL' } }
Icon NameUse For
AIRPLANETravel, flights
BOOKMARKSave, reference, links
BUSTransport, transit
CARDriving, transport
CLOCKTime, duration, schedule
CONFIRMATION_NUMBER_ICONTickets, bookings
DESCRIPTIONDocuments, files
DOLLARMoney, pricing, cost
EMAILEmail, messages
INVITEInvitations
MAP_PINLocation, address
MEMBERSHIPMembers, users
MULTIPLE_PEOPLETeams, groups
OFFERDeals, promotions
PERSONIndividual user
PHONEPhone number, calls
SHOPPING_CARTCommerce, purchases
STARRating, favourite, important
STOREShop, retail
TICKETTickets, events
VIDEO_CAMERAVideo, meetings

For icons not in the list, use iconUrl with any publicly accessible image (square, ideally 24x24 or 48x48 pixels).

Threading

Thread messages together using threadKey:

// First message — creates thread
const response = await sendCard(webhookUrl, card, {
  threadKey: 'deploy-2026-02-16'
});

// Reply to thread — append &messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD
const threadUrl = `${webhookUrl}&messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD`;
await sendCard(threadUrl, replyCard, {
  threadKey: 'deploy-2026-02-16'
});

The threadKey is a client-assigned string. Use consistent keys for related messages (e.g., deploy-{date}, alert-{id}).

Common Patterns

Notification Card

import { buildCard, sendCard } from './assets/card-builder';
import { sendWebhook } from './assets/webhook-sender';

const card = buildCard({
  cardId: 'deploy-notification',
  title: 'Deployment Complete',
  subtitle: 'production - v2.1.0',
  imageUrl: 'https://example.com/your-icon.png',
  sections: [{
    widgets: [
      { decoratedText: { topLabel: 'Environment', text: 'Production' } },
      { decoratedText: { topLabel: 'Version', text: 'v2.1.0' } },
      { decoratedText: { topLabel: 'Status', text: '*Healthy*', startIcon: { knownIcon: 'STAR' } } },
      { buttonList: { buttons: [{ text: 'View Deployment', onClick: { openLink: { url: 'https://dash.example.com' } } }] } }
    ]
  }]
});

Digest Card (Weekly Summary)

const digest = buildCard({
  cardId: 'weekly-digest',
  title: 'Weekly Summary',
  subtitle: `${count} updates this week`,
  sections: [
    {
      header: 'Highlights',
      widgets: items.map(item => ({
        decoratedText: { text: item.title, bottomLabel: item.date }
      }))
    },
    {
      widgets: [{
        buttonList: {
          buttons: [{ text: 'View All', onClick: { openLink: { url: dashboardUrl } } }]
        }
      }]
    }
  ]
});

Error Prevention

MistakeFix
**bold** in textUse *bold* (single asterisks)
[text](url) linksUse `<url\
Missing cardsV2 wrapperWrap card in { cardsV2: [{ cardId, card }] }
Thread replies not threadingAppend &messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD to webhook URL
Webhook returns 400Check JSON structure — common issue is missing text or cardsV2 at top level
Card not showingEnsure sections has at least one widget

Asset Files

FilePurpose
assets/types.tsTypeScript type definitions for cardsV2
assets/card-builder.tsUtility to build card messages
assets/webhook-sender.tsPOST to webhook with error handling

Related skills

How it compares

Use google-chat-messages for incoming-webhook card JSON; use Google Chat Apps SDK skills when OAuth bots are required.

FAQ

Does Google Chat use Markdown?

No; it uses *bold*, _italic_, and ~strikethrough~ formatting syntax.

Where do webhook URLs belong?

Environment variables or a secrets manager, never hardcoded in source.

What card format is used?

cardsV2 with headers, sections, widgets, and optional buttonList actions.

Is Google Chat Messages safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.