AppsPricingBlogTry it
Jira Service Desk logo
Microsoft Teams logo

Connect Jira Service Desk to Microsoft Teams

Use 2 documented Jira Service Desk triggers to run 12 documented Microsoft Teams actions.

2 source triggers
12 target actions
Reverse direction supported

Why Connect Jira Service Desk & Microsoft Teams?

Start with a Jira Service Desk event

Choose from 2 documented triggers, including New Request Created, Request Status Updated.

Run a Microsoft Teams action

Send the event into one of 12 documented actions, such as Create Channel, Get Chat Message, Get Current User.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

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

Microsoft Teams logo

Microsoft Teams

Triggers (6)

New Channel

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

polling
New Channel Message

Emit new event when a new message is posted in a channel. See the documentation

polling
New Chat

Emit new event when a new chat is created. See the documentation

polling
New Chat Message

Emit new event when a new message is received in a chat. See the documentation

polling
New Team

Emit new event when a new team is joined by the authenticated user. See the documentation

polling
New Team Member

Emit new event when a new member is added to a team. See the documentation

polling

Actions (12)

Create Channel

Create a new channel in Microsoft Teams. See the docs here

Get Chat Message

Get a specific message from a chat. See the documentation

Get Current User

Returns the authenticated Microsoft Teams user's ID, display name, email, and principal name via Microsoft Graph. Call this first when the user says 'my channels', 'my chats', or needs identity context. Use the returned id to identify the sender in **Send Channel Message** or **Send Chat Message** results. See the documentation.

List Channel Messages

Lists messages in a Microsoft Teams channel. See the documentation

List Channels

Lists all channels in a Microsoft Team. See the docs here

List Chats

Lists all chat conversations for the authenticated user. See the documentation

List Messages in Chat

Get the list of messages in a chat. See the documentation

List Shifts

Get the list of shift instances for a team. See the documentation

List Teams

Lists all teams the authenticated user has joined. See the documentation

Search Messages

Search for email or chat messages. See the documentation

Send Channel Message

Send a message to a team's channel. Optionally include inline images via hostedContents. See the documentation

Send Chat Message

Send a message to a team's chat. Optionally include inline images via hostedContents. See the docs here

Integration Features

2 documented Jira Service Desk triggers
12 documented Microsoft Teams actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Microsoft Teams to Jira Service Desk direction

Capability Examples

Jira Service Desk trigger → Microsoft Teams action

Catalog example
Jira Service DeskJira Service Desk

New Request Created

Microsoft TeamsMicrosoft Teams

Create Channel

Microsoft Teams trigger → Jira Service Desk action

Reverse direction
Microsoft TeamsMicrosoft Teams

New Channel

Jira Service DeskJira Service Desk

Create Comment on Request

How It Works

1

Connect Apps

Authenticate your Jira Service Desk and Microsoft Teams accounts

2

Choose a Trigger

Select a documented Jira Service Desk event

3

Choose an Action

Select the documented Microsoft Teams operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 2 documented Jira Service Desk triggers.

Automated Actions

Run one of 12 documented Microsoft Teams actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Microsoft Teams logoJira Service Desk logo

Reverse Integration Available

Also connect Microsoft Teams to Jira Service Desk for bidirectional automation

View Integration
Jira Service Desk logo

All Jira Service Desk Integrations

Explore all available Jira Service Desk connections

View All Integrations
Microsoft Teams logo

All Microsoft Teams Integrations

Explore all available Microsoft Teams connections

View All Integrations

Ready to Connect Jira Service Desk & Microsoft Teams?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free