How to send Jira Service Management alerts to Google Chat

Service desk teams often want new requests, priority changes and customer replies in Google Chat. The hard part is keeping internal agent notes out of those spaces.

What to send (and what never to send)

Option 1: Google's Jira app in Chat

Google Chat includes a Jira app you can add to a space or open in a direct message. Admins install the matching Chat plugin from the Atlassian Marketplace, connect the Jira site, then subscribe spaces to projects. It is fine for personal alerts and simple project subscriptions.

Limits for service desks: space subscriptions are project-oriented, filters are coarser than JQL routes, and you still need to check whether internal notes can appear depending on how the connection is set up. Card clicks sometimes fail for users ("something went wrong"), which is a common complaint when teams rely on Chat cards alone.

Option 2: Jira Automation plus a Google Chat webhook

  1. In Google Chat, open the space, then space name, Apps & integrations, Webhooks, Add webhook. Copy the URL.
  2. In Jira, create an automation rule on your service project. Useful triggers: Issue created, Issue transitioned, Comment added.
  3. Add conditions (priority, request type, or status) so the space only sees actionable work.
  4. Add a Send web request action that POSTs a small JSON body with the issue key, summary and status to the webhook URL (same pattern as other Jira webhook rules).

Watch the Comment added trigger closely. Automation does not always make it obvious whether a comment is public or internal. If your rule posts comment bodies, double-check that internal notes never leave Jira. Automation run limits also apply on your Jira plan.

Incoming webhooks need Google Workspace Business or Enterprise, and your Workspace admin must allow them. See the broader Jira to Google Chat guide for webhook setup details.

Option 3: Threadline for Jira

Threadline for Jira is built for filtered Jira and Jira Service Management notifications in Google Chat. You paste a webhook URL, pick projects and events, optionally narrow with issue type, priority, status, labels, assignee or JQL, and keep one thread per request. Internal JSM comments are never posted. Burst batching, daily digests, quiet hours and a delivery log keep the space readable. It runs on Atlassian Forge, is free for up to 10 users, then $0.80 per user per month through Atlassian, and is pending Atlassian Marketplace review. Setup steps are on the support page.

Practical setup checklist

  1. Create a dedicated Chat space for the service queue (or one space per queue if teams are separate).
  2. Confirm Workspace allows incoming webhooks before you debug missing Webhooks menus.
  3. Start with created and priority-changed events only. Add public comments later if the volume is still useful.
  4. Send a test message, then create a throwaway request and an internal note to verify the note never appears in Chat.
  5. For calmer mornings, add a daily digest instead of every status flicker.

Frequently asked questions

Do Jira Service Management internal comments go to Google Chat?

They should not. Prefer a path that never posts internal notes. Threadline for Jira never posts internal JSM comments. If you use Automation, avoid posting comment bodies unless you are sure the trigger is public-only.

Can I route different JSM queues to different Chat spaces?

Yes. Use one webhook and one route or Automation rule per space, filtered by project, request type, JQL or labels.

Does this work on free Gmail?

No. Google Chat incoming webhooks need Google Workspace Business or Enterprise with webhooks allowed by your admin.

Is there an official Google Chat integration for JSM?

Google's Jira app in Chat covers many software and work projects. For service desks that need stricter filters and a hard block on internal notes, Automation webhooks or a dedicated Forge app such as Threadline for Jira are usually safer.

Related guides