Connect Jira Service Desk to HubSpot

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 comment to a thread. See the documentation

Adds a contact to a specific static list. See the documentation

MCP and AI agents: **Prefer this action** when the user wants to **leave a note on a HubSpot contact** using a **contact ID** and note text. Exposes only hubspot, contactId, and noteBody (no engagement-type step, no reloadProps, no dynamic HubSpot schema fields). Do **not** use **Create Engagement** for this workflow. For every writable note property or non-contact associations, use **Create Note** instead. See the documentation

Archives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentation

Create a batch of companies in Hubspot. See the documentation

Create or update a batch of contacts by its ID or email. See the documentation

Update a batch of companies in Hubspot. See the documentation

Upsert a batch of companies in Hubspot. See the documentation

Clone a marketing email in HubSpot. See the documentation

Clone a site page in Hubspot. See the documentation

Create a new workflow. See the documentation

Create an association (link) between two CRM records. For example, associate a contact with a company, a deal with a contact, or a ticket with a company. Common association type IDs: contact→company (1), company→contact (2), deal→contact (3), contact→deal (4), deal→company (5), company→deal (6), ticket→contact (15), contact→ticket (16), ticket→company (26), company→ticket (25). See the documentation

Create associations between objects. See the documentation

Creates a new blog post in HubSpot. See the documentation

Create a WhatsApp, LinkedIn, or SMS message. See the documentation

Create a company in Hubspot. See the documentation

Create a contact workflow in Hubspot. See the documentation

Create a new CRM record (contact, company, deal, ticket, etc.). Pass property values as a JSON object in the properties parameter. Use **Search Properties** to discover available fields for the object type, **Get Properties** to find valid enum values (e.g. lifecyclestage, dealstage), and **List Pipelines and Stages** to find valid pipeline/stage IDs for deals and tickets. Use **List Owners** to find valid hubspot_owner_id values. See the documentation

Create a new custom object in Hubspot. See the documentation

Create a deal in Hubspot. See the documentation

Create a **task, meeting, email, call, or note** engagement with optional associations. Set **Engagement Type** and pass engagement fields in **Object Properties** (HubSpot property names, e.g. hs_note_body for notes). No reloadProps step and no **CONFIGURE_COMPONENT** requirement: association fields accept raw HubSpot IDs (use **Search CRM** or the Associations API to resolve associationType when needed). For **only** a note on a contact by ID, **Add Note to Contact** (hubspot-add-note-to-contact) is still simpler. See the documentation

Create a form in HubSpot. See the documentation

Create a landing page in Hubspot. See the documentation

Create a lead in Hubspot. See the documentation