Connect Jira Service Desk to Pipedrive

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

Adds a new activity. Includes more_activities_scheduled_in_context property in response's additional_data which indicates whether there are more undone activities scheduled with the same deal, person or organization (depending on the supplied data). See the Pipedrive API docs for Activities here. For info on adding an activity in Pipedrive

Adds a new deal. See the Pipedrive API docs for Deals here

Adds labels to a lead, person, deal, or organization in Pipedrive. See the documentation

Create a new lead in Pipedrive. See the documentation

Adds a new note. For info on adding an note in Pipedrive

Adds a new organization. See the Pipedrive API docs for Organizations here

Adds a new person. See the Pipedrive API docs for People here

Get all leads from Pipedrive. See the documentation

Get a deal by its ID. See the documentation

Get a lead by its ID. See the documentation

Get details of a person by their ID. See the documentation

List deals in your Pipedrive account. See the documentation

Retrieves available options for the Lead Label IDs field.

Retrieves available options for the Organization Label IDs field.

Retrieves available options for the Person Label IDs field.

Retrieves available options for the User ID field.

Merge two deals in Pipedrive. See the documentation

Merge two persons in Pipedrive. See the documentation

Remove duplicate notes from an object in Pipedrive. See the documentation for getting notes and deleting notes

Removes one or more specific labels from a lead, person, deal, or organization in Pipedrive, leaving all other labels intact. See the documentation

Search for leads by name or email. See the documentation

Search for notes in Pipedrive. See the documentation

Searches all Persons by name, email, phone, notes and/or custom fields. This endpoint is a wrapper of /v1/itemSearch with a narrower OAuth scope. Found Persons can be filtered by Organization ID. See the Pipedrive API docs here

Updates the properties of a deal. See the Pipedrive API docs for Deals here