Google Chat webhook kind #14

New Issue

michael · 2026-01-19T18:31:14Z

michael commented

2026-01-19 18:31:14 +00:00

Originally created by @fraserhess on GitHub.

I'm requesting support for Google Chat webhooks as a kind. The generic messages result in an HTTP 400 error because there's only two fields supported in the payload by Google Chat: text and thread.

The text field supports some basic formatting: newlines, bold, italics, strikethrough, monospaced, monospaced block, bulleted list, and hyperlinks.

Example curl command:

curl -X POST "https://chat.googleapis.com/v1/spaces/XXXXX/messages?key=YYYYYY&token=ZZZZ" -H "Content-Type: application/json; charset=UTF-8" -d '{"text":"# Hello *team*!\nThis message was sent via curl."}'

A full URL to a test space in Google Chat can be provided privately for testing.

References:
https://developers.google.com/workspace/chat/quickstart/webhooks
https://developers.google.com/workspace/chat/format-messages

Originally created by @fraserhess on GitHub. I'm requesting support for Google Chat webhooks as a kind. The generic messages result in an HTTP 400 error because there's only two fields supported in the payload by Google Chat: `text` and `thread`. The `text` field supports some basic formatting: newlines, bold, italics, strikethrough, monospaced, monospaced block, bulleted list, and hyperlinks. Example curl command: ``` curl -X POST "https://chat.googleapis.com/v1/spaces/XXXXX/messages?key=YYYYYY&token=ZZZZ" -H "Content-Type: application/json; charset=UTF-8" -d '{"text":"# Hello *team*!\nThis message was sent via curl."}' ``` A full URL to a test space in Google Chat can be provided privately for testing. References: https://developers.google.com/workspace/chat/quickstart/webhooks https://developers.google.com/workspace/chat/format-messages

michael added the enhancement label 2026-01-19 18:31:14 +00:00

michael commented

2026-01-19 18:31:14 +00:00

@fraserhess commented on GitHub:

There is also a cardsV2 option that creates richer output and experiences but the JSON is much more complex

{
  "cardsV2": [
    {
      "cardId": "FA2F044B-ADA4-422A-8470-D1468511BED1",
      "card": {
        "header": {
          "title": "Setup Manager: Started",
          "subtitle": "MacBook Pro"
        },
        "sections": [
          {
            "header": "Details",
            "collapsible": false,
            "widgets": [
              {
                "decoratedText": {
                  "topLabel": "Serial",
                  "text": "DHGG6LQFW2"
                }
              },
              {
                "decoratedText": {
                  "topLabel": "macOS",
                  "text": "26.2 (Build 25C5048a)"
                }
              }
            ]
          }
        ]
      }
    }
  ]
}

Reference:
https://developers.google.com/workspace/chat/api/reference/rest/v1/cards

@fraserhess commented on GitHub: There is also a `cardsV2` option that creates richer output and experiences but the JSON is much more complex ``` { "cardsV2": [ { "cardId": "FA2F044B-ADA4-422A-8470-D1468511BED1", "card": { "header": { "title": "Setup Manager: Started", "subtitle": "MacBook Pro" }, "sections": [ { "header": "Details", "collapsible": false, "widgets": [ { "decoratedText": { "topLabel": "Serial", "text": "DHGG6LQFW2" } }, { "decoratedText": { "topLabel": "macOS", "text": "26.2 (Build 25C5048a)" } } ] } ] } } ] } ``` <img width="303" height="244" alt="Image" src="https://github.com/user-attachments/assets/9d0160b1-754e-4785-b1c8-b07bfb52f95b" /> Reference: https://developers.google.com/workspace/chat/api/reference/rest/v1/cards

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#14