ChatBridge documentation
Requirements
- Jira Cloud, and a Jira administrator to install and configure the app.
- A Google Workspace account with Google Chat. Incoming webhooks are not available for personal Gmail accounts.
- Incoming webhooks allowed in your Workspace (Admin console → Apps → Google Workspace → Google Chat → Chat apps). They are allowed by default.
1. Create a webhook in Google Chat
- Open the Google Chat space that should receive Jira updates.
- Click the space name at the top → Apps & integrations → Webhooks.
- Click Add webhook, name it (for example "Jira") and save.
- Copy the webhook URL. It starts with
https://chat.googleapis.com/v1/spaces/.
Treat the URL like a password. Anyone who has it can post to the space. ChatBridge stores it encrypted and never displays it again.
2. Add a rule in Jira
- In Jira, go to Settings (⚙) → Apps → ChatBridge for Google Chat.
- Enter a name, paste the webhook URL and choose the events:
Event Posted when Issue created A new issue is created. Status changed The issue moves to another status, e.g. To Do → In Progress. Assignee changed The issue is assigned or unassigned. Comment added Someone comments. The message includes the first 300 characters. Comments restricted to a role or group are announced without their text, and Jira Service Management internal notes are labelled "Internal note". - Optionally add a JQL filter. Only issues matching it are posted. Leave it empty to post every issue.
- Click Save rule, then Send test to confirm the space receives messages.
JQL examples
| Goal | JQL |
|---|---|
| One project | project = PAY |
| Urgent work only | priority in (Highest, High) |
| Bugs in two projects | project in (WEB, MOBILE) AND type = Bug |
| Exclude a confidential project | project != LEGAL |
You can create up to 50 rules, for example one per team space.
How messages behave
- Threads: all messages about one issue go to the same thread in a space.
- Duplicates: the same change repeated within 30 seconds is posted once.
- Rate limits: Google Chat accepts about one message per second per space. ChatBridge retries automatically when a space is busy.
- Changes made by ChatBridge itself are ignored, so it never posts about its own activity.
Troubleshooting
| "Send test" says… | What to do |
|---|---|
| Google Chat rejected the webhook | Copy the full URL again from the space, including key= and token=. Delete the rule and add it again. |
| Webhook was removed or webhooks are disabled | Check the webhook still exists in the space, or ask your Workspace admin to allow incoming webhooks. |
| The Chat space no longer exists | Create a new webhook in an existing space. |
| Rate limiting | Wait a minute and try again. |
Test works but no messages arrive? Check that the issue matches the rule's JQL and that the right events are selected.
Migrating from another Google Chat integration
Atlassian ends support for the older Connect app framework on January 31, 2027. If you use a Connect-based Google Chat integration, plan the switch before then.
- List the spaces your current integration posts to and what each one receives.
- Install ChatBridge and create one rule per space, translating your project or filter choices into JQL.
- Run both integrations for a few days and compare what each space receives.
- Remove the old integration's webhooks from your spaces, then uninstall it from Jira.
Uninstalling
Uninstall from Settings → Apps → Manage apps. Remove the webhooks from your Google Chat spaces as well. What happens to stored rules is described in our privacy policy.
Still stuck? Contact support.