Send a Slack alert when a new Jira Software issue is created

Point a Jira Software webhook for created issues at this workflow and each new issue posts a message to a Slack channel with the details you choose, such as the summary, project and reporter.

Webhook

Slack

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.0k sites Free to import

The Send a Slack alert when a new Jira Software issue is created workflow on the FlowMattic canvas, with 2 steps across Webhook, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

New Jira issues can sit unnoticed until someone opens the board. A short message in the Slack channel your team already reads puts each new bug or request in front of people when it is raised. This workflow passes Jira's own webhook data straight into that message.

The first step is FlowMattic's Webhook trigger, which gives you a URL to receive data. In Jira, you create a webhook that sends the issue created event to that URL. FlowMattic's own Jira Software trigger works the same way, by receiving webhooks you configure, so this generic version does the same job. Each delivery starts a run, and the issue data from Jira is passed to Slack, where Send Channel Message posts in the channel you pick.

Which events arrive depends on how you set up the webhook in Jira. Select only issue creation there, or edits and comments will post messages too. Anyone who has the URL can send data to it unless you turn on the Webhook trigger's authentication setting, so check what your Jira webhook can send before you enable it.

Bug reports for a dev team

QA logs a bug in Jira. The developers' Slack channel gets a message with the issue key, summary and priority so someone can pick it up.

Service requests from other departments

Marketing files a request in a Jira project. The team that handles requests sees it in their Slack channel as soon as it is raised.

One project's alerts in a client channel

Limit the Jira webhook to one project with a JQL filter in Jira, and new issues in that project post to the shared Slack channel you have with the client.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Webhook Capture Webhook Response
Receives the data Jira sends to this workflow's webhook URL. Set up a webhook in Jira for the issue created event, then create a test issue so FlowMattic captures the fields.
Step 2Action
Slack Send Channel Message
Sends the new-issue alert to the Slack channel you choose. Connect your Slack workspace, pick the channel, and build the text from the Jira issue fields, such as the summary and a link to the issue.

What you need

FlowMatticCore
Slack 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.

In Jira's webhook settings, tick only the issue created event. Other events sent to the same URL would each post a Slack message.
To alert only for urgent work, add a Filter after the webhook that continues when the issue's priority equals Highest or the value your Jira uses.
For a private Slack channel, swap the step for Send Private Channel Message. To reach one person, use Send Direct Message instead.

Questions about this workflow

Why does this Jira to Slack workflow use a generic Webhook trigger?

FlowMattic's Jira Software trigger is itself a webhook you configure in Jira, so the generic Webhook receives the same data. Either way, you register the URL in Jira.

Will Jira issue updates or comments also post in Slack?

Only if your Jira webhook sends those events. Select issue created alone in Jira's webhook settings to keep the channel to new issues.

Can I include a link to the Jira issue in the Slack message?

Yes, if you build it from the data Jira sends, such as your site address plus the issue key. Create a test issue and check the captured fields first.

Can someone else send fake data to the webhook URL?

Anyone with the URL could, unless authentication is on. Turn on the Webhook trigger's authentication setting if your Jira webhook can send the key or signature it expects.