Connect OpenAI (ChatGPT) to Jira Service Desk

The Chat API, using the gpt-3.5-turbo or gpt-4 model. See the documentation

Chat using the web search tool. See the documentation

Chat with your models and allow them to invoke functions. Optionally, you can build and invoke workflows as functions. See the documentation

Chat with your files knowledge base (vector stores). See the documentation

Summarizes text using the Chat API. See the documentation

Classify items into specific categories using the Chat API. See the documentation

Translate text from one language to another using the Chat API. See the documentation

Transcribes audio into the input language. See the documentation

Creates an image given a prompt returning a URL to the image. See the documentation

Get a vector representation of a given input that can be easily consumed by machine learning models and algorithms. See the documentation

OpenAI recommends using the **Chat** action for the latest gpt-3.5-turbo API, since it's faster and 10x cheaper. This action creates a completion for the provided prompt and parameters using the older /completions API. See the documentation

Send a message or question about an image and receive a response. See the documentation

Cancels a run that is in progress. See the documentation

Sends a message and generates a response, storing the message history for a continuous conversation. See the documentation

Send a chat via the Responses API, mixing built-in tools and MCP server tools. See the documentation.

Generates audio from the input text. See the documentation

Creates an assistant with a model and instructions. See the documentation

Creates and executes a batch from an uploaded file of requests. See the documentation

Creates a job that fine-tunes a specified model from a given dataset. See the documentation

Classifies if text is potentially harmful. See the documentation

Creates a thread with optional messages and metadata, and optionally runs the thread using the specified assistant. See the documentation

Create a vector store. See the documentation

Create a vector store file. See the documentation

Deletes a specified file from OpenAI. 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