AppsPricingBlogTry it
Calendly logo
Jira Service Desk logo

Connect Calendly to Jira Service Desk

Use 4 documented Calendly triggers to run 12 documented Jira Service Desk actions.

4 source triggers
12 target actions
Reverse direction supported

Why Connect Calendly & Jira Service Desk?

Start with a Calendly event

Choose from 4 documented triggers, including New Event Scheduled, New Invitee Canceled, New Invitee Created.

Run a Jira Service Desk action

Send the event into one of 12 documented actions, such as Create Comment on Request, Create Incident, Create Request.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Calendly logo

Calendly

Triggers (4)

New Event Scheduled

Emit new event when a event is scheduled.

polling
New Invitee Canceled

Emit new event when an event is canceled.

polling
New Invitee Created

Emit new event when a new event is scheduled.

polling
New Routing Form Submission Created

Emit new event when a new routing form submission is created.

polling

Actions (7)

Create a Scheduling Link

Creates a single-use scheduling link. See the documentation

Create Invitee No Show

Marks an Invitee as a No Show in Calendly. See the documentation.

Get Event

Gets information about an Event associated with a URI. See the documentation.

List Event Invitees

List invitees for an event. See the documentation

List Events

List events for an user. See the documentation

List User Availability Schedules

List the availability schedules of the given user. See the documentation

List Webhook Subscriptions

Get a list of Webhook Subscriptions for an Organization or User with a UUID.

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

Integration Features

4 documented Calendly triggers
12 documented Jira Service Desk actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported Jira Service Desk to Calendly direction

Capability Examples

Calendly trigger → Jira Service Desk action

Catalog example
CalendlyCalendly

New Event Scheduled

Jira Service DeskJira Service Desk

Create Comment on Request

Jira Service Desk trigger → Calendly action

Reverse direction
Jira Service DeskJira Service Desk

New Request Created

CalendlyCalendly

Create a Scheduling Link

How It Works

1

Connect Apps

Authenticate your Calendly and Jira Service Desk accounts

2

Choose a Trigger

Select a documented Calendly event

3

Choose an Action

Select the documented Jira Service Desk operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented Calendly triggers.

Automated Actions

Run one of 12 documented Jira Service Desk actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

Jira Service Desk logoCalendly logo

Reverse Integration Available

Also connect Jira Service Desk to Calendly for bidirectional automation

View Integration
Calendly logo

All Calendly Integrations

Explore all available Calendly connections

View All Integrations
Jira Service Desk logo

All Jira Service Desk Integrations

Explore all available Jira Service Desk connections

View All Integrations

Ready to Connect Calendly & Jira Service Desk?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free