AppsPricingBlogTry it
Jira Service Desk logo
Salesforce logo

Connect Jira Service Desk to Salesforce

Use 2 documented Jira Service Desk triggers to run 24 documented Salesforce actions.

2 source triggers
24 target actions
Reverse direction supported

Why Connect Jira Service Desk & Salesforce?

Start with a Jira Service Desk event

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

Run a Salesforce action

Send the event into one of 24 documented actions, such as Add Contact to Campaign, Add Lead to Campaign, Convert SOAP XML Object to JSON.

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

Salesforce logo

Salesforce

Triggers (10)

Case Updated (Instant, of Selectable Type)

Emit new event when a case is updated. See the documentation

webhook
Email Template Updated (Instant, of Selectable Type)

Emit new event when an email template is updated. See the documentation

webhook
Knowledge Article Updated (Instant, of Selectable Type)

Emit new event when a knowledge article is updated. See the documentation

webhook
New Case (Instant, of Selectable Type)

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

webhook
New Deleted Record (Instant, of Selectable Type)

Emit new event when a record of the selected object type is deleted. See the documentation

webhook
New Email Template (Instant, of Selectable Type)

Emit new event when an email template is created. See the documentation

webhook
New Knowledge Article (Instant, of Selectable Type)

Emit new event when a knowledge article is created. See the documentation

webhook
New Outbound Message (Instant)

Emit new event when a new outbound message is received in Salesforce.

webhook
New Record (Instant, of Selectable Type)

Emit new event when a record of the selected object type is created. See the documentation

webhook
New Updated Record (Instant, of Selectable Type)

Emit new event when a record of the selected type is updated. See the documentation

webhook

Actions (24)

Add Contact to Campaign

Adds an existing contact to an existing campaign. See the documentation

Add Lead to Campaign

Adds an existing lead to an existing campaign. See the documentation

Convert SOAP XML Object to JSON

Converts a SOAP XML Object received from Salesforce to JSON

Create Account

Creates a Salesforce account. See the documentation

Create Accounts (Batch)

Create multiple Accounts in Salesforce using Bulk API 2.0. See the documentation

Create Attachment

Creates an Attachment on a parent object. See the documentation

Create Campaign

Creates a marketing campaign. See the documentation

Create Case

Creates a Case, which represents a customer issue or problem. See the documentation

Create Case Comment

Creates a Case Comment on a selected Case. See the documentation

Create Contact

Creates a contact. See the documentation

Create Content Note

Creates a content note. See the documentation and Set Up Notes.

Create Event

Creates an event. See the documentation

Create Lead

Creates a lead. See the documentation

Create Note

Creates a note. See the documentation

Create Opportunities (Batch)

Create multiple Opportunities in Salesforce using Bulk API 2.0. See the documentation

Create Opportunity

Creates an opportunity. See the documentation

Create Record

Create a record of a given object. See the documentation

Create Record

Create a new Salesforce record of any object type. Use **Describe Object** first if you're unsure what fields are available or required. For picklist fields, use the API value from **Describe Object**, not the display label. **Common required fields:** - Account: Name - Contact: LastName - Lead: LastName, Company - Opportunity: Name, StageName, CloseDate - Case: Subject - Task: Subject - Event: Subject, StartDateTime, EndDateTime To add a Contact/Lead to a Campaign, create a CampaignMember: {"CampaignId": "701xxx", "ContactId": "003xxx"} or {"CampaignId": "701xxx", "LeadId": "00Qxxx"}.

Create Task

Creates a task. See the documentation

Create User

Creates a Salesforce user. See the documentation

Delete Note Or Content Note

Delete a note or content note from a Salesforce record. See the documentation

Delete Opportunity

Deletes an opportunity. See the documentation

Delete Record

Permanently deletes a Salesforce record (moves to Recycle Bin for 15 days). Use **SOQL Query** to find the record ID if you only have the record name.

Delete Record

Deletes an existing record in an object. See the documentation

Integration Features

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

Capability Examples

Jira Service Desk trigger → Salesforce action

Catalog example
Jira Service DeskJira Service Desk

New Request Created

SalesforceSalesforce

Add Contact to Campaign

Salesforce trigger → Jira Service Desk action

Reverse direction
SalesforceSalesforce

Case Updated (Instant, of Selectable Type)

Jira Service DeskJira Service Desk

Create Comment on Request

How It Works

1

Connect Apps

Authenticate your Jira Service Desk and Salesforce accounts

2

Choose a Trigger

Select a documented Jira Service Desk event

3

Choose an Action

Select the documented Salesforce 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 24 documented Salesforce 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.

Salesforce logoJira Service Desk logo

Reverse Integration Available

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

All Salesforce Integrations

Explore all available Salesforce connections

View All Integrations

Ready to Connect Jira Service Desk & Salesforce?

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

Get Started Free