AppsPricingBlogTry it
Slack logo
Jira Service Desk logo

Connect Slack to Jira Service Desk

Automate workflows and sync data between Slack and Jira Service Desk with AI-powered automation

5-minute setup
Enterprise secure
No coding required

Why Connect Slack & Jira Service Desk?

Intelligent Automation Workflows

Leverage 9 available triggers from Slack to execute 12 targeted actions in Jira Service Desk automatically.

Eliminate Manual Data Entry

Replace time-consuming manual processes with intelligent automation that keeps Slack and Jira Service Desk perfectly synchronized.

Real-time Business Intelligence

Create a unified data flow between Slack and Jira Service Desk for instant insights and improved decision-making across your tech stack.

Available Triggers & Actions

Slack logo

Slack

Triggers (9)

New Channel Created (Instant)

Emit new event when a new channel is created.

webhook
New Interaction Events (Instant)

Emit new events on new Slack interactivity events sourced from Block Kit interactive elements, Slash commands, or Shortcuts.

webhook
New Keyword Mention (Instant)

Emit new event when a specific keyword is mentioned in a channel

webhook
New Message In Channels (Instant)

Emit new event when a new message is posted to one or more channels

webhook
New Private Channel Created

Emit new event when a new private channel is created. See the documentation

polling
New Reaction Added (Instant)

Emit new event when a member has added an emoji reaction to a message

webhook
New Saved Message (Instant)

Emit new event when a message is saved. Note: The endpoint is marked as deprecated, and Slack might shut this off at some point down the line.

webhook
New User Added (Instant)

Emit new event when a new member joins a workspace.

webhook
New User Mention (Instant)

Emit new event when a username or specific keyword is mentioned in a channel

webhook

Actions (24)

Send Message to Channel

Send a message to a public or private channel. See the documentation

Add Emoji Reaction

Add an emoji reaction to a message. See the documentation

Add Reaction

Add an emoji reaction to a message. Accepts a channel ID or channel name (resolved automatically). Use **Get Channel History** or **Search** to find the message timestamp. Emoji name should be without colons (e.g. thumbsup, fire, heart). See the documentation

Approve Workflow

Suspend the workflow until approved by a Slack message. See the documentation

Archive Channel

Archive a channel. See the documentation

Browse Files

List files shared in a channel or across the workspace. Accepts a channel ID or channel name (resolved automatically). Filter by file type (e.g. images, pdfs, snippets). Returns file metadata including name, type, size, and download URL. See the documentation

Build and Send a Block Kit Message

Configure custom blocks and send to a channel, group, or user. See the documentation.

Create a Channel

Create a new channel. See the documentation

Create Reminder

Create a reminder. See the documentation

Delete File

Delete a file. See the documentation

Delete Message

Delete a message. See the documentation

Edit Message

Edit an existing message. Accepts a channel ID or channel name (resolved automatically). Requires the message timestamp (ts) from **Get Channel History** or **Post Message**. You can only edit messages posted by the same token/user. See the documentation

Find Message

Find a Slack message. See the documentation

Find User by Email

Find a user by matching against their email. See the documentation

Find User by ID

Find a user by their ID. Returns user profile information including name, email (requires users:read.email scope), timezone, and status. See the documentation

Get Channel Details

Retrieve details for a Slack channel by selecting it or providing an ID. See the documentation

Get Channel History

Read the recent message history from a specific channel. Accepts a channel ID or channel name (resolved automatically). Use this when you want to see a channel's latest messages — unlike **Search** which finds messages by keyword. Returns messages with text, timestamps (ts), reactions, and user IDs. Message timestamps can be used with **Get Thread Replies**, **Edit Message**, and **Add Reaction**. See the documentation

Get Current User

Retrieve comprehensive context about the authenticated Slack member, combining auth.test, users.info, users.profile.get, and team.info payloads. Returns the user’s profile (name variants, email, locale, timezone, status, admin flags), raw auth test data, and workspace metadata (domain, enterprise info, icons). Ideal when you need to confirm which user token is active, tailor messages to their locale/timezone, or ground an LLM in the member’s role and workspace before executing other Slack actions. See Slack API docs.

Get File

Return information about a file. See the documentation

Get Thread Replies

Retrieve all replies in a message thread. Accepts a channel ID or channel name (resolved automatically). Use **Get Channel History** or **Search** to find the parent message's timestamp (thread_ts). Returns the parent message followed by all replies in chronological order. See the documentation

Get User Details

Retrieve the authenticated user's identity and workspace context. Returns user ID, name, email, timezone, profile, and workspace metadata. Call this first in any session to establish who you are — other tools like **Search** and **List Channels** can then filter by your user ID. See the documentation

Invite User to Channel

Invite a user to an existing channel. See the documentation

Kick User

Remove a user from a conversation. See the documentation

List Channels

Return a list of all channels in a workspace. See the documentation

Jira Service Desk logo

Jira Service Desk

Triggers (2)

New Request Created

Emit new event when a customer request is created. See the documentation

polling
Request Status Updated

Emit new event when a customer request is updated. See the documentation

polling

Actions (12)

Create Comment on Request

Create a comment on a customer request. See the documentation

Create Incident

Creates a new incident request in a Jira Service Desk. Auto-discovers the best-matching request type (prefers types named 'incident' or 'problem') and, if serviceDeskId is omitted, auto-discovers it from the user's existing requests. Use **List Sites** first to obtain the required cloudId. serviceDeskId is optional — if not provided, the tool calls **List My Requests** to discover it automatically. Returns the new request including its issueKey and issueId. See the documentation

Create Request

Creates a new customer request. See the documentation

Get Current User

Returns the authenticated user's account_id, display_name, and email from Atlassian. Use this to identify who is logged in, or to filter requests by the current user's account_id. No cloudId required — this uses the Atlassian Identity API directly. See the documentation

Get Request

Fetches the full details of a Jira Service Desk request including its field values and complete comment thread in a single response. Use this to summarize a ticket without needing follow-up calls. Use **List Sites** first to obtain the required cloudId. Use **List My Requests** to find the issueKey of a request (e.g. IT-42). See the documentation

Get Request Status

Returns the status history of a Jira Service Desk request — the current status plus all previous states with timestamps. Use this to understand how a request has progressed through the workflow. Use **List Sites** first to obtain the required cloudId. Use **List My Requests** to find the issueKey (e.g. IT-42). See the documentation

List Cloud ID Options

Retrieves available options for the Cloud ID field.

List My Requests

Lists Jira Service Desk requests owned or participated in by the current user. Defaults to open requests owned by the current user. Use **List Sites** first to obtain the required cloudId. Each result includes issueKey, issueId, and request field values (summary, status). requestStatus: OPEN_REQUESTS (default), CLOSED_REQUESTS, or ALL_REQUESTS. requestOwnership: OWNED_REQUESTS (default) or PARTICIPATED_REQUESTS. See the documentation

List Request Transitions

Lists the available workflow transitions for a Jira Service Desk request — returns each transition's id and name. **Call this before Transition Request** to obtain valid transitionId values. Use **List Sites** first to obtain the required cloudId. Use **List My Requests** or **Get Request** to find the issueKey (e.g. IT-42). See the documentation

List Sites

Returns all Atlassian cloud sites accessible to the authenticated user. **Call this tool first** to obtain the cloudId (returned as id) required by every other Jira Service Desk tool. Each site includes its id (cloudId), name, and url. See the documentation

Transition Request

Transitions a Jira Service Desk request to a new workflow status. Use **List Request Transitions** first to get valid transitionId values for the request. Use **List Sites** to obtain the required cloudId. Use **List My Requests** or **Get Request** to find the issueKey (e.g. IT-42). Optionally include a comment to explain the transition. See the documentation

Update Issue Fields

Updates fields on an existing Jira Service Desk request via the Jira platform API. Use this to change the summary, priority, description, or other fields after a request has been created. Use **List Sites** first to obtain the required cloudId. Use **List My Requests** or **Get Request** to find the issueKey (e.g. IT-42). fields is a JSON object of field name-value pairs. Example: {"summary": "Updated title", "priority": {"name": "High"}}. See the documentation

Integration Features

Real-time data synchronization
Bi-directional sync capabilities
Custom field mapping
Advanced filtering options
Error handling & retry logic
Activity monitoring & logs

Popular Workflows

When Slack trigger → Create/Update in Jira Service Desk

Most Popular
SlackSlack

New Channel Created (Instant)

Jira Service DeskJira Service Desk

Create Comment on Request

When Jira Service Desk trigger → Update Slack

Bi-directional
Jira Service DeskJira Service Desk

New Request Created

SlackSlack

Send Message to Channel

How It Works

1

Connect Apps

Authenticate your Slack and Jira Service Desk accounts

2

Map Fields

Choose which data fields to sync between apps

3

Set Triggers

Define when and how data should be synchronized

Automate

Sit back and let AI handle the automation

Frequently Asked Questions

Integration Benefits

Real-time Data Sync

Automatic synchronization between Slack and Jira Service Desk with 11 public triggers available for instant updates.

Automated Actions

Execute 36 public actions automatically across both platforms without manual intervention.

Enterprise Security

Industry-standard encryption, OAuth 2.0 authentication, and SOC 2 compliance for secure data transfer.

Quick Setup

Connect Slack and Jira Service Desk in minutes with our guided setup wizard and pre-configured templates.

Custom Field Mapping

Map any field between Slack and Jira Service Desk with intelligent suggestions and validation.

Error Handling

Automatic retry logic, detailed error logs, and smart notifications keep your integration running smoothly.

Jira Service Desk logoSlack logo

Reverse Integration Available

Also connect Jira Service Desk to Slack for bidirectional automation

View Integration
Slack logo

All Slack Integrations

Explore all available Slack connections

View All Integrations
Jira Service Desk logo

All Jira Service Desk Integrations

Explore all available Jira Service Desk connections

View All Integrations

Ready to Connect Slack & Jira Service Desk?

Join thousands of users automating their workflows with Mazaal AI