AppsPricingBlogTry it
Jira Service Desk logo
Gmail logo

Connect Jira Service Desk to Gmail

Use 2 documented Jira Service Desk triggers to run 20 documented Gmail actions.

2 source triggers
20 target actions
Reverse direction supported

Why Connect Jira Service Desk & Gmail?

Start with a Jira Service Desk event

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

Run a Gmail action

Send the event into one of 20 documented actions, such as Add Label to Email, Approve Workflow, Archive Email.

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

Gmail logo

Gmail

Triggers (5)

New Attachment Received

Emit new event for each attachment in a message received. This source is capped at 100 max new messages per run.

polling
New Email Matching Search

Emit new event when an email matching the search criteria is received. This source is capped at 100 max new messages per run.

polling
New Email Received

Emit new event when a new email is received.

polling
New Labeled Email

Emit new event when a new email is labeled.

polling
New Sent Email

Emit new event for each new email sent. (Maximum of 100 events emited per execution)

polling

Actions (20)

Add Label to Email

Add label(s) to an email message. See the docs

Approve Workflow

Suspend the workflow until approved by email. See the documentation

Archive Email

Archive an email message. See the documentation

Bulk Archive Emails

Archive multiple emails at once. See the documentation

Create Draft

Create a draft from your Google Workspace email account. See the documentation

Create Label

Create a new label in the connected account. See the documentation

Delete Email

Moves the specified message to the trash. See the documentation

Download Attachment

Download an attachment by attachmentId to the /tmp directory. See the documentation

Find Email

Find an email using Google's Search Engine. See the docs

Get Current User

Returns the authenticated Gmail user's name, email address, and mailbox stats (total messages and threads). Call this first when the user says 'my emails', 'my inbox', or needs identity context. Use the returned emailAddress to identify the user's own messages in **Find Email** results. See the documentation.

Get Send As Alias

Get a send as alias for the authenticated user. See the documentation

List Labels

List all the existing labels in the connected account. See the docs

List Send as a Delegate Options

Retrieves available options for the Send as a Delegate field.

List Send As Aliases

List all send as aliases for the authenticated user. See the documentation

List Signature Options

Retrieves available options for the Signature field.

List Thread Messages

List messages in a thread. See the docs

Remove Label from Email

Remove label(s) from an email message. See the docs

Send Email

Send an email from your Google Workspace email account. See the documentation

Update Signature for Email in Organization

Update the signature for a specific email address in an organization. A Google Cloud service account with delegated domain-wide authority is required for this action. See the documentation

Update Signature for Primary Email Address

Update the signature for the primary email address. See the documentation

Integration Features

2 documented Jira Service Desk triggers
20 documented Gmail actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Gmail to Jira Service Desk direction

Capability Examples

Jira Service Desk trigger → Gmail action

Catalog example
Jira Service DeskJira Service Desk

New Request Created

GmailGmail

Add Label to Email

Gmail trigger → Jira Service Desk action

Reverse direction
GmailGmail

New Attachment Received

Jira Service DeskJira Service Desk

Create Comment on Request

How It Works

1

Connect Apps

Authenticate your Jira Service Desk and Gmail accounts

2

Choose a Trigger

Select a documented Jira Service Desk event

3

Choose an Action

Select the documented Gmail 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 20 documented Gmail 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.

Gmail logoJira Service Desk logo

Reverse Integration Available

Also connect Gmail 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
Gmail logo

All Gmail Integrations

Explore all available Gmail connections

View All Integrations

Ready to Connect Jira Service Desk & Gmail?

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

Get Started Free