Documentation
Last updated: October 3, 2026
1. Before you start
- A Jira Cloud site with the app installed from the Atlassian Marketplace. Shared spaces are set up by a Jira administrator.
- A Google Workspace Business or Enterprise account with Google Chat. Your Workspace administrator must allow incoming webhooks. Personal Gmail accounts can't create webhooks.
- A computer: Google Chat doesn't let you create webhooks from its mobile app.
2. Create a webhook in Google Chat
- Open Google Chat in a web browser and go to the space that should receive the notifications (create a new space if you need one).
- Click the space name at the top → Apps & integrations.
- Click Add webhooks, give it a name such as “Jira” (the avatar URL is optional) and click Save.
- Next to the new webhook open the More menu (⋮) → Copy link. The link starts with
https://chat.googleapis.com/v1/spaces/.
Treat the webhook link like a password. Anyone who has it can post in the space. Paste it only into the app. If it leaks, delete the webhook in Google Chat and create a new one.
If you don't see Add webhooks, your Google Workspace administrator has turned incoming webhooks off for your organization. Google may rename these menus over time; Google's own guide is here.
Comparing options? See 3 ways to send Jira notifications to Google Chat.
3. Add a space in Jira
- In Jira, go to Settings (⚙) → Apps and, in the left menu, open Sago Alerts — Google Chat. Only Jira administrators see this page. The first time, Jira may show Atlassian's Allow access screen: the app uses it to check, as you, that you are a Jira administrator.
- Click Add space and fill in the form (see the table below).
- Press Send test. A message “Connected to Jira ✅” should appear in the space within a few seconds.
- Press Save. The space appears in the list with its filter and events.
| Field | What it does |
|---|---|
| Name | A label for you, e.g. “Backend team”. It also appears in the test message and in the daily summary title. |
| Google Chat webhook URL | The link you copied. After saving, the page only shows a masked version; leave the field empty to keep the saved link. |
| Projects | Empty = all projects. |
| Extra JQL filter | Optional. See Filter by project and JQL. |
| Notify me when | The events this space receives. See Choose what to notify. |
| Only for status changes into | Optional; appears when “Status changes” is checked. See Only certain status changes. |
| Message style | Card with details, or compact (one line). |
| Group updates of the same issue in one thread | On by default. See Threads. |
| Message language | English, Spanish or Portuguese. |
| Daily summary | Optional. See Daily summary. |
You can add as many spaces as you need, each with its own filters, events, style and language. The same Jira update can go to several spaces.
4. Choose what to notify
| Option | Notifies when | Default |
|---|---|---|
| An issue is created | A new issue is created. | ✓ |
| Status changes | The issue moves to another status. | ✓ |
| Assignee changes | The issue is assigned, reassigned or unassigned. | ✓ |
| A comment is added | A new comment is posted. Editing a comment doesn't notify. | ✓ |
| An issue is resolved | A resolution is set. Reopening (clearing the resolution) doesn't count. | ✓ |
| Priority changes | The priority changes. | |
| Other fields change | Any other field changes: summary, description, labels, due date, custom fields… Jira's background fields (Rank, time tracking and similar) are ignored. | |
| An issue is deleted | An issue is deleted. See Deleted issues. |
Pick at least one event, or turn on the daily summary. When one edit changes several things (for example status and assignee), the space gets one message: the headline shows the most important change and the card shows the rest.
5. Filter by project and JQL
Projects limits the space to one or more projects. Extra JQL filter adds any JQL condition. Both are combined with AND:
project in ("WEB", "API") AND (your JQL)
Some useful filters:
labels = backend
priority in (High, Highest)
issuetype = Bug AND component = "Payments"
assignee in membersOf("support-team")
- The JQL is validated when you save; if Jira rejects it, the error is shown under the field. Tip: try the query in Jira's issue search first.
- When an update arrives, Jira itself checks whether the issue matches the filter, as it is after the change.
- The daily summary uses the same projects and JQL.
6. Only certain status changes
When Status changes is checked you can fill Only for status changes into with statuses from your Jira, for example Done and In Review. Then only transitions into those statuses notify; other transitions are skipped. Leave it empty to get every status change.
If the same edit also changes something else the space listens to (for example the assignee), the message is still sent, with that other change as the headline.
7. Card or compact view
- Card with details: a header with the issue key, summary and project; rows for Status (with “from → to” when it changed), Assignee and Priority; up to four other changed fields with their new value; the comment text (first 600 characters, mentions as names); and an Open in Jira button that goes to the issue or the comment.
- Compact (one line): issue key, summary, what changed, a short comment excerpt (200 characters) and a link. Good for busy spaces.
8. Threads
With Group updates of the same issue in one thread on, the first message about an issue starts a thread and later updates of that issue reply in it. If Google Chat can't find the thread, it starts a new one. With it off, every update is a separate message. The daily summary and test messages never go into issue threads.
9. Message language
Each space chooses English, Spanish or Portuguese for the app's own text (headlines, labels, buttons). Issue content, such as summaries, comments and status names, stays as it is in Jira. The settings pages follow each user's Jira language (English, Spanish or Portuguese; other languages show English).
10. Daily summary
- Turn on Daily summary and choose the hour, the time zone (your browser's by default) and the days (Monday to Friday by default).
- The summary takes the 50 most recently updated issues of the last 24 hours that match the space's projects and JQL, counts them by status and lists the 10 most recent with links, plus a See all in Jira button. If more than 50 issues changed, the subtitle shows “50+” and the counts cover only those 50; the button opens the full list in Jira.
- The app checks every hour: the summary arrives during the chosen hour, or up to 2 hours later if a run was missed. Never more than one per day.
- If nothing changed, you get a one-line “No issues were updated in the last 24 h.”
- A space can receive only the summary: uncheck every event and keep the summary on.
11. Personal notifications
Every Jira user can get notifications about their own work in a Google Chat space of their own, without an administrator.
- In Google Chat, create a space just for yourself and add a webhook to it (see step 2).
- In Jira, open your profile picture (the profile menu in the top navigation) and choose Sago Alerts — Google Chat.
- Paste the webhook link and choose your reasons (table below).
- Press Send test, then Save. The first time, Jira asks you to allow the app to check your permissions: accept it. Before every personal message the app asks Jira, as you, whether you can see the issue (and the comment). Without that check, nothing is sent.
| Reason | You're notified when | Default |
|---|---|---|
| An issue is assigned to me | Someone assigns an issue to you, or creates it already assigned to you. | ✓ |
| Someone mentions me | You're @mentioned in an issue or a comment. | ✓ |
| My assigned issues change status or get comments | An issue assigned to you gets an important change: status, comment, resolution, priority or assignee. | ✓ |
| Issues I reported change | The same important changes, on issues you reported. | |
| Issues I watch change | The same important changes, on issues you watch. |
- Ignore my own changes (on by default) skips updates you made yourself.
- You get one message per update even if several reasons apply; the card's subtitle says why (for example “Assigned to you”).
- Messages go only to the space whose webhook you pasted. Use a private space: if you paste the webhook of a shared space, everyone in it will read your notifications.
- Turn off deletes your subscription and your webhook link from the app. It also works when the app's license is not active.
- Deactivated Jira accounts don't receive personal notifications. When an Atlassian account is closed or deleted, the app removes that person's subscription at its next weekly check. Administrators can't delete another person's subscription from the app; uninstalling the app removes all of them.
- Personal notifications don't include deleted issues.
12. Restricted comments and internal notes
Comments restricted to a group or project role, and Jira Service Management internal notes, are handled carefully:
- Spaces never receive anything about them, because people in the Google Chat space may not be allowed to see them.
- Comments restricted to a group or role usually don't reach the app at all: Atlassian doesn't send apps the events of comments they can't see. In practice you get no notification for them, not even a personal one.
- Internal notes in service projects do reach the app. A personal notification then says only “… added a restricted comment (open it in Jira)”, without the text, and only if Jira confirms that you can see that note.
- @mentions inside a restricted comment don't trigger “mentioned you”.
13. Deleted issues
Once an issue is deleted Jira can't check it against JQL anymore, so:
- Spaces without filters receive the deletion.
- Spaces filtered only by project receive it if the issue belonged to one of those projects.
- Spaces with an extra JQL filter don't receive deletions. The settings page warns you about this.
14. Pause, edit or delete a space
- On/Off switch in the list: pauses the space and keeps its settings.
- Edit: change anything. Leave the webhook field empty to keep the saved link, or paste a new one to replace it.
- Send test: checks that the saved webhook still works.
- Delete: removes the space's settings and its stored webhook link from the app's storage. It also works when the license is not active. Messages already posted in Google Chat stay there.
15. Trial and license
- The app is sold through the Atlassian Marketplace: free for sites with up to 10 users and paid per user above that, with a 30-day free trial. Atlassian handles quotes, billing and invoices.
- If the license is not active (trial ended or subscription cancelled), the app stops sending notifications and summaries and the settings pages show a notice. Settings are kept while the app is installed, and notifications resume when the license is active again. Updates made in the meantime are not sent afterwards.
- While the license is not active you can still delete spaces (admin page) and turn off personal notifications (personal page).
- If you uninstall the app, Atlassian keeps its stored data for up to 28 days and then deletes it permanently. Reinstalling doesn't restore the previous settings and we don't offer data recovery, so note your settings down first if you may come back. See the privacy policy.
16. Known limitations
- Delay. Atlassian delivers Jira events to apps asynchronously. Most arrive within seconds, but Atlassian documents that they can take up to about 3 minutes, and longer during platform incidents (see the Atlassian Developer status page).
- Atlassian Forge quotas and limits. The app runs on Atlassian Forge and is subject to its platform quotas and limits: how long each function may run, how many invocations and Jira API calls an app can make, and how much it can store and read. If a limit is reached, notifications or summaries can be delayed or skipped, and Atlassian can temporarily suspend an app that exceeds its limits. Atlassian publishes them in Forge platform quotas and limits.
- Google Chat rate limit. Google accepts about 1 message per second per space, shared by all the webhooks in that space. The app retries (up to 4 attempts within about 20 seconds), but during bulk edits of many issues some messages may still be dropped. For noisy projects use filters, a separate space or the daily summary.
- Edited comments. Editing a comment doesn't notify, so a person newly @mentioned in an edited comment isn't notified.
- Status names. Status, resolution and priority names come from Jira's change history and may appear in the Jira site's default language rather than in each user's language.
- One-way. Notifications go from Jira to Google Chat. You can't reply to Jira or create issues from Google Chat.
- Fixed layout. Messages can be customized by style, threads and language, not with templates.
- Lengths. Comment excerpts are capped at 600 characters (200 in compact view) and summaries at 180.
- Daily summary size. The counts by status cover at most the 50 most recently updated issues; above that the summary shows “50+”.
- Restricted comments. Comments restricted to a group or role usually never reach the app, so they produce no notification.
- Inactive license. Updates made while the license was inactive are not sent later.
- Personal check. If you remove the app's access from your Atlassian account settings, personal notifications stop until you save your personal page again.
17. Troubleshooting
“That is not a Google Chat webhook URL”
The link must start with https://chat.googleapis.com/v1/spaces/ and contain key= and token=. Copy it again with More (⋮) → Copy link in Google Chat.
The test fails with “Google Chat HTTP …”
- 404: the webhook or the space was deleted. Create a new webhook and paste it.
- 403: Google refused the message, usually because webhooks were turned off for your organization or the webhook was removed.
- 400: the link is damaged. Copy it again.
- 429: too many messages to that space right now. Wait a minute and try again.
The test works but updates don't arrive
- Check that the space is On, that the issue's project is selected (or the list is empty) and that the issue matches the JQL after the change.
- Check that the event is checked and, for status changes, the Only for status changes into list.
- Restricted comments never reach spaces, and spaces with JQL don't receive deletions.
- Check that the app's license is active (the settings page shows a notice if not).
- Wait up to 3 minutes: Atlassian may deliver the event late.
Personal notifications don't arrive
- Save the personal page again and accept the permission prompt if Jira shows it.
- Ignore my own changes hides updates you made yourself.
- You only get updates for issues (and comments) that you can see in Jira.
- Comments restricted to a group or role usually never reach the app, so they produce no notification.
The daily summary doesn't arrive
Check the hour, the time zone and the days. The summary is sent during the chosen hour or up to 2 hours later.
Still stuck? See Support.