AppsPricingBlogTry it
Airtable logo
Jira Service Desk logo

Connect Airtable to Jira Service Desk

Use 8 documented Airtable triggers to run 12 documented Jira Service Desk actions.

8 source triggers
12 target actions
Reverse direction supported

Why Connect Airtable & Jira Service Desk?

Start with a Airtable event

Choose from 8 documented triggers, including New Field Created (Instant), New or Modified Field (Instant), New or Modified Records (Instant).

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

Airtable logo

Airtable

Triggers (8)

New Field Created (Instant)

Emit new event when a field is created in the selected table. See the documentation

webhook
New or Modified Field (Instant)

Emit new event when a field is created or updated in the selected table

webhook
New or Modified Records (Instant)

Emit new event for each new or modified record in a table or view

webhook
New or Modified Records in View

Emit new event for each new or modified record in a view

polling
New Record Created, Updated or Deleted (Instant)

Emit new event when a record is added, updated, or deleted in a table or selected view.

webhook
New Record(s) Created (Instant)

Emit new event for each new record in a table

webhook
New Records in View

Emit new event for each new record in a view

polling
New, Modified or Deleted Records

Emit new event each time a record is added, updated, or deleted in an Airtable table. Supports tables up to 10,000 records

polling

Actions (18)

Create Comment

Create a comment on a selected record. See the documentation

Create Field

Create a new field in a table. See the documentation

Create Multiple Records

Create one or more records in a table in a single operation with an array. See the documentation

Create or Update Record

Create a new record or update an existing one. See the documentation

Create Single Record

Adds a record to a table.

Create Table

Create a new table. See the documentation

Delete Record

Delete a selected record from a table. See the documentation

Get Record

Get data of a selected record from a table. See the documentation

Get Record Or Create

Get a specific record, or create one if it doesn't exist. See the documentation

List Bases

Get the list of bases that can be accessed. See the documentation

List Records

Retrieve records from a table, optionally sorting and filtering results. See the documentation

List Records in View

Retrieve records from a view, optionally sorting and filtering results. See the documentation

List Tables

Get a list of tables in the selected base. See the documentation

Search Records

Search for a record by formula or by field value. See the documentation

Update Comment

Update an existing comment on a selected record. See the documentation

Update Field

Update an existing field in a table. See the documentation

Update Record

Update a single record in a table by Record ID. See the documentation

Update Table

Update an existing table. See the documentation

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

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

Capability Examples

Airtable trigger → Jira Service Desk action

Catalog example
AirtableAirtable

New Field Created (Instant)

Jira Service DeskJira Service Desk

Create Comment on Request

Jira Service Desk trigger → Airtable action

Reverse direction
Jira Service DeskJira Service Desk

New Request Created

AirtableAirtable

Create Comment

How It Works

1

Connect Apps

Authenticate your Airtable and Jira Service Desk accounts

2

Choose a Trigger

Select a documented Airtable 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 8 documented Airtable 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 logoAirtable logo

Reverse Integration Available

Also connect Jira Service Desk to Airtable for bidirectional automation

View Integration
Airtable logo

All Airtable Integrations

Explore all available Airtable 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 Airtable & Jira Service Desk?

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

Get Started Free