Notify for Google Chat
Setup, how the filters work, and what to check when a message doesn't arrive.
Requirements
Incoming webhooks in Google Chat require a Google Workspace
account. They are not available on personal @gmail.com accounts —
the "Add webhooks" menu simply will not appear. Your Workspace administrator
also has to permit webhooks: Admin console → Apps → Google Workspace →
Google Chat → Chat apps.
Setup
- In Jira: Settings → Apps → Google Chat notifications.
- In Google Chat: open the space → click its name → Apps & integrations → Add webhooks → give it a name → Save → ⋮ → Copy link.
- Paste that link into the rule's Google Chat room address field.
- Pick projects and filters, then Save.
- Press Send a test message. It goes straight to the room, bypassing every filter.
The room address is a credential: anyone who has it can post to that space. Treat it like a password, and cover it in screenshots.
How rules work
A rule is one room plus a set of conditions. Add as many rules as you need — each posts to its own room. An event is sent when every condition set on the rule is satisfied.
| Field | What it does |
|---|---|
| Projects | One rule can cover any number of projects. Empty means all of them — a rule with nothing selected watches the whole site. |
| Events | Issue created, issue updated, new comment. Unticking one silences it for this rule only. |
| Fields | Applies to updates only. Tick Status and the rule stays quiet while people edit descriptions. Empty means any change qualifies. |
| People and role | Restrict the rule to specific people. Four roles are available: assignee, reporter, mentioned in a comment, and watching the issue. They combine with or: with "assignee" and "mentioned in a comment" both ticked, either one is enough. Empty means anyone. |
| Status transition | Fire only when an issue moves between two named statuses. Fill both sides for an exact transition, or one side for "anything leaving In Review". Applies to updates only; leave both empty to ignore transitions entirely. |
| Threading | On, every message about one issue lands in a single thread. Off, each update appears in the main flow. |
| Quiet window | At most one message per issue per N seconds. A burst of edits becomes
one message instead of twenty. 0 disables it. |
Who appears in the people list
Jira only lets apps see the people who can be assigned in a project, so the list follows the projects selected in the rule. Start typing to search — in a large site the full list is not shown, and the search is what you want.
When a message doesn't arrive
The settings page has a Recent deliveries list at the bottom. Every attempt appears there with its outcome, and that line usually names the problem:
- sent — the message reached Google. If you can't see it in the room, check whether threading put it into an older thread.
- held back — the quiet window suppressed it. Expected.
- error: Google Chat replied 404 — the webhook was deleted or the address is wrong. Create a new one and paste it in.
- error: Google Chat replied 400 — the address is malformed, usually a truncated copy. Copy it again in full.
- nothing listed at all — no rule matched. Widen the filters, or press "Send a test message" to confirm the connection itself works.
Licensing
Free for up to 10 users. Without an active licence the app keeps your rules but stops sending, and the settings page says so. Nothing is lost; notifications resume when the licence does.
What the app can and cannot do
- Read-only access to Jira. It cannot change or delete anything.
- One outbound destination: the Google Chat webhook you configure. The platform prevents it from reaching any other host.
- No issue content is stored. Rules and the last 40 delivery records live in Atlassian's own storage.