How to send Jira notifications to a Google Chat space

There are three ways to get Jira updates into Google Chat. Two of them start with the same step: an incoming webhook for the space.

1. Create a webhook for the space

1. In Google Chat, open the space and click its name at the top.
2. Choose Apps & integrations → Webhooks → Add webhook.
3. Give it a name, for example Jira, and save.
4. Copy the URL. Anyone with it can post to the space, so treat it like a password.

Webhooks need a Google Workspace account; they aren’t available for personal Gmail accounts. If you don’t see Webhooks, your Workspace admin has turned them off.

2. Option A: a Jira Automation rule

Jira Automation is built into Jira Cloud and can post to the webhook. Good for one or two simple messages.

1. In your project, open Project settings → Automation (in newer Jira: the space’s settings) and create a rule.
2. Pick a trigger, for example Work item transitioned (called Issue transitioned on older sites), and optionally limit it to a status.
3. Add the action Send web request:
   • Web request URL: the webhook URL
   • HTTP method: POST
   • Header: Content-Type = application/json
   • Web request body: Custom data, for example:

{
  "text": "*{{issue.key}}* {{issue.summary.jsonEncode}} moved to {{issue.status.name}} by {{initiator.displayName}}\n{{issue.url}}"
}

.jsonEncode keeps quotes in a summary from breaking the message.

Trade-offs: each rule sends one kind of message, so several events or spaces mean several rules. Every run counts toward your plan’s monthly automation limit. Messages don’t group into one thread per issue unless you add thread parameters yourself. And if the webhook stops working, you only see it in the rule’s audit log.

3. Option B: a Marketplace app (Herald)

Herald is our app for exactly this job. You paste the webhook into Jira once, then choose the projects, work types, status changes, fields or JQL a space should get.

• Updates arrive as cards, one thread per issue; bulk edits become one summary.
• A delivery log for each space, and an email to admins if a space stops receiving.
• Runs on Atlassian Forge and doesn’t count toward your automation limits.
• Free for up to 10 users; larger sites pay per user after a 30-day trial.

Setup takes about two minutes: see the documentation.

4. Option C: Google’s Jira bot

Google offers a free Jira app for Chat. Besides space notifications it can send personal notifications and create or show issues from Chat with commands such as /jira_create. It needs a sign-in from Chat to Jira, which is where most setup problems happen; see our fixes.

5. Which one to choose