Post Jira Software issue changes to a Discord channel for the team
When Jira Software sends an issue change to your FlowMattic webhook, this workflow posts a message about it in the Discord channel you pick, so the team sees updates where it already talks.
Webhook
Discord2 steps Setup ~5 min Used on 1.8k sites Free to import
What this workflow does
Developers and stakeholders rarely sit in Jira all day, but many of them keep Discord open. This workflow passes Jira Software issue changes into a Discord channel, so a status change or a new comment shows up in the conversation instead of waiting in someone's notifications.
Step one is FlowMattic's Webhook trigger, which gives you a unique URL. In Jira, you create a webhook that points at that URL and choose which issue events it reports. FlowMattic's own Jira Software trigger is also a webhook receiver, so the generic one does the same job here. Every request Jira sends starts a run, and the issue data in it becomes values you can map.
The Discord step, Send Channel Message, then posts a message to the channel you select. You write the message yourself and drop in the parts of the Jira payload you want, such as the issue key, summary or new status. There is no Filter as imported, so each request Jira sends becomes one Discord message.
Sprint updates in a team channel
Point the Jira webhook at issue updates for your sprint project, and the dev channel gets a short post each time an issue changes, without anyone pasting links.
Keeping a client server informed
An agency that runs a Discord server with a client posts Jira changes for that client's project into a shared channel, so the client follows progress without a Jira seat.
A quiet feed for QA
Send only bug issues from Jira to a dedicated QA channel, where testers see each change to the bugs they reported.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Webhook Capture Webhook ResponseGives you a webhook URL to add to Jira Software's webhook settings. Each request Jira sends there starts a run, and the issue details in the payload become fields you can map. Trigger one issue change after import to capture them.
- Discord Send Channel Message
Sends a Discord message into the channel you select for each Jira request. Connect Discord, pick the channel, and compose the message from the Jira values captured by the webhook, such as the issue key, title and status.
What you need
- FlowMatticCore
- Discord AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- When you create the webhook in Jira, tick only the issue events your team needs. Fewer events sent means fewer Discord posts.
- Add a Filter after the trigger that continues only for the issue changes you want posted, for example issues in one project or with a given priority. A test run shows which payload fields hold those values.
- Turn on the Webhook trigger's authentication setting if Jira can send the key or signature it expects, so requests from anywhere else don't post to your channel.
- Build the issue link into the message by combining your Jira site address with the issue key, so readers can click straight through.
Questions about this workflow
Why does this use a Webhook trigger instead of a Jira app trigger?
FlowMattic's Jira Software trigger is itself a webhook receiver that you configure in Jira. The generic Webhook works the same way: Jira posts issue events to the URL, and FlowMattic runs the workflow for each one.
Which Jira issue changes get posted to Discord?
Whatever the Jira webhook is set to send. Every request that reaches the URL creates one Discord message, since the template has no Filter. Limit the events in Jira, or add a Filter in FlowMattic, to cut the noise.
Can anyone who has the webhook URL post to my Discord channel?
Only while the trigger's authentication is off. The Webhook trigger has a setting to require authentication on incoming requests, using a key the caller sends or signature verification for senders that sign their webhooks.
Will Jira issues changed before setup appear in Discord?
No. Only changes Jira reports to the webhook after you add the URL in Jira and turn the workflow on are posted. Earlier history stays in Jira.
More Notifications & Alerts workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted