AppsPricingBlogTry it
Jira Service Desk logo
Canny logo

Connect Jira Service Desk to Canny

Automate workflows and sync data between Jira Service Desk and Canny with AI-powered automation

5-minute setup
Enterprise secure
No coding required

Why Connect Jira Service Desk & Canny?

Intelligent Automation Workflows

Leverage 2 available triggers from Jira Service Desk to execute 10 targeted actions in Canny automatically.

Eliminate Manual Data Entry

Replace time-consuming manual processes with intelligent automation that keeps Jira Service Desk and Canny perfectly synchronized.

Real-time Business Intelligence

Create a unified data flow between Jira Service Desk and Canny for instant insights and improved decision-making across your tech stack.

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

Canny logo

Canny

Triggers (3)

New Comment Created

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

polling
New Vote Created

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

polling
Post Status Changed

Emit new event when the status of a post is changed. See the documentation

polling

Actions (10)

Change Post Status

Change the status of a post. See the documentation

Create Comment

Create a comment. See the documentation

Create Post

Create a post. See the documentation

Get Post

Get a post. See the documentation

List Board ID Options

Retrieves available options for the Board ID field.

List Category ID Options

Retrieves available options for the Category ID field.

List Comment ID Options

Retrieves available options for the Comment ID field.

List Company ID Options

Retrieves available options for the Company ID field.

List Tag ID Options

Retrieves available options for the Tag ID field.

List User ID Options

Retrieves available options for the User ID field.

Integration Features

Real-time data synchronization
Bi-directional sync capabilities
Custom field mapping
Advanced filtering options
Error handling & retry logic
Activity monitoring & logs

Popular Workflows

When Jira Service Desk trigger → Create/Update in Canny

Most Popular
Jira Service DeskJira Service Desk

New Request Created

CannyCanny

Change Post Status

When Canny trigger → Update Jira Service Desk

Bi-directional
CannyCanny

New Comment Created

Jira Service DeskJira Service Desk

Create Comment on Request

How It Works

1

Connect Apps

Authenticate your Jira Service Desk and Canny accounts

2

Map Fields

Choose which data fields to sync between apps

3

Set Triggers

Define when and how data should be synchronized

Automate

Sit back and let AI handle the automation

Frequently Asked Questions

Integration Benefits

Real-time Data Sync

Automatic synchronization between Jira Service Desk and Canny with 5 public triggers available for instant updates.

Automated Actions

Execute 22 public actions automatically across both platforms without manual intervention.

Enterprise Security

Industry-standard encryption, OAuth 2.0 authentication, and SOC 2 compliance for secure data transfer.

Quick Setup

Connect Jira Service Desk and Canny in minutes with our guided setup wizard and pre-configured templates.

Custom Field Mapping

Map any field between Jira Service Desk and Canny with intelligent suggestions and validation.

Error Handling

Automatic retry logic, detailed error logs, and smart notifications keep your integration running smoothly.

Canny logoJira Service Desk logo

Reverse Integration Available

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

All Canny Integrations

Explore all available Canny connections

View All Integrations

Ready to Connect Jira Service Desk & Canny?

Join thousands of users automating their workflows with Mazaal AI