Connect Salesforce to Jira Service Desk

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

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

Converts a SOAP XML Object received from Salesforce to JSON

Creates a Salesforce account. See the documentation

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

Creates an Attachment on a parent object. See the documentation

Creates a marketing campaign. See the documentation

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

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

Creates a contact. See the documentation

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

Creates an event. See the documentation

Creates a lead. See the documentation

Creates a note. See the documentation

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

Creates an opportunity. See the documentation

Create a record of a given object. See the documentation

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"}.

Creates a task. See the documentation

Creates a Salesforce user. See the documentation

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

Deletes an opportunity. See the documentation

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.

Deletes an existing record in an object. See the documentation

Create a comment on a customer request. See the documentation

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

Creates a new customer request. See the documentation

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

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

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

Retrieves available options for the Cloud ID field.

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

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

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

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

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