Resources · Make integration

Jira Cloud Platform Make integrationAutomate Jira Cloud Platform with Make.

What if your Jira issues opened, moved and filled themselves? The Jira Cloud Platform Make integration gives you 40 modules: 2 triggers, 28 actions and 10 searches. This guide is for teams who live in Jira and want to link their account, then build a first working scenario.

Try the Jira Cloud Platform integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Jira Cloud Platform Make integration do?

The Jira Cloud Platform Make integration links your Jira account to Make so that issues, comments, watchers, versions and components change without anyone clicking in Jira. You build a scenario, which is the automation itself: a chain of modules, each one a brick that watches, acts or searches.

Tickets that open themselves. A form, a support inbox or a CRM feeds Create an Issue, then Add an Attachment puts the customer's file on the new issue. Nobody retypes a request by hand.

Release notes that stay honest. Create a Project Version prepares the release, and Search Issues pulls the tickets that belong to it, so a product manager can send the list to a shared document or a chat channel.

Alerts the right people read. The instant Watch Issues trigger hears a ticket event as it happens, Get an Issue reads its details, and a message goes out to the channel that owns the work.

Two limits come from the Make documentation. The instant trigger needs an account with the Administer Jira global permission to create its webhook, and a Jira instance holds up to 100 active admin webhooks. Anything the 40 modules do not cover goes through Make an API Call. If you are weighing tools, read n8n vs Make, and check Make pricing before you scale. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect Jira Cloud Platform to Make?

  1. 01

    Create an API token in Atlassian

    Sign in at https://id.atlassian.com/manage/api-tokens, click Create API token, give it a Label you will recognize later, then click Create. Click Copy right away and keep the token somewhere safe.

  2. 02

    Add a Jira module and open the connection

    In a Make scenario, add any Jira Cloud Platform module and click Add next to the Connection field. A connection is your Jira account linked to Make once, then reused by every Jira module. Naming it is optional.

  3. 03

    Fill in the three fields and save

    Type your Service URL, which is the address of your Jira site, then your Username, and paste the token into API Token. Click Save. Make can now list your projects and issues inside each module.

First scenario

Your first scenario with Jira Cloud Platform

GoalWhen a request arrives from another app, Make creates a Jira issue and attaches the file that came with it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where requests land first, such as your form tool or your inbox, and choose its module.

  2. 02

    Add Create an Issue

    Click the + on the right, search Jira Cloud Platform and pick Create an Issue. Click Create a connection if you have not linked your account yet, then choose the project Make lists for you.

  3. 03

    Map the request into the issue

    Fill the issue fields with data from the first module: map what the request says into the fields Make lists for your project. Each request travels as a bundle, one item passed from module to module.

  4. 04

    Attach the file

    Add Add an Attachment after Create an Issue. Point it to the issue that the previous module just created, then map the file from the first module so it lands on the right ticket.

  5. 05

    Test with Run once

    Send a test request, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open Jira and check the new issue and its attachment.

  6. 06

    Schedule and switch it on

    Click the clock on the first module to set Scheduling; a new scenario runs every 15 minutes by default. Then switch the scenario on so each new request becomes a Jira issue.

Triggers

What starts a Jira Cloud Platform scenario

2 modules start a scenario when something happens in Jira Cloud Platform. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Jira Cloud Platform as soon as it happens.

Jira Cloud Platform1Watch Issues

Watch Issues

Instant trigger

In Make“Triggers when a ticket event occurs.”

This version of Watch Issues starts your scenario the moment a ticket event happens in Jira, so the next modules work on fresh data instead of waiting for the next check.

How it fires
instant, the app calls Make through a webhook as soon as it happens (the lightning badge on the module).
When to use it
pick it when a delay matters, for example to alert an on-call team the moment a critical bug is filed.
Watch out
creating the webhook requires the Administer Jira global permission, and a Jira instance accepts up to 100 active admin webhooks.
Jira Cloud Platform2Watch Issues

Watch Issues

Scheduled trigger

In Make“Triggers when an issue is created or updated.”

The scheduled Watch Issues picks up issues that were created or updated since its last look, and hands each one to the rest of the scenario as a separate bundle.

How it fires
scheduled, Make checks the app on the scenario's schedule (the clock badge), every 15 minutes by default and never under 15 minutes on the Free plan.
When to use it
choose it when your account lacks admin rights for webhooks, or when a short delay is fine, such as copying updated issues to a reporting sheet.
Watch out
each check uses operations, the unit Make counts on your plan.
Modules

Everything the Jira Cloud Platform modules can do

Jira Cloud Platform gives you 38 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Jira Cloud Platform1

Add an Attachment

Action

In Make“Adds a new attachment to a ticket.”

Puts a file from another module onto an existing ticket, so screenshots, contracts or logs sit where the team already looks.

When to use it
right after Create an Issue, when a form or email brought a file that support needs to see.
Watch out
on the Free plan Make handles files up to 5 MB, so large logs may need a paid plan.
Jira Cloud Platform2

Add an Issue Comment

Action

In Make“Adds a comment to an issue.”

Writes a comment on an issue for you, which keeps the story of a ticket inside Jira instead of scattered across chat threads.

When to use it
when a customer replies by email or a deployment tool finishes, and the assignee should read it in the ticket.
Watch out
if a scheduled Watch Issues watches the same project, a new comment may count as an update there; add a filter so the scenario does not answer its own notes.
Jira Cloud Platform3

Add a Watcher

Action

In Make“Adds a user as a watcher to an issue.”

Subscribes a person to an issue so Jira keeps them informed of every change, without asking them to click Watch themselves.

When to use it
when an account manager should follow every ticket opened for their client, or a lead wants eyes on escalations.
Watch out
you need the user first, so place Search Users before this module when all you have is a name or an email.
Jira Cloud Platform4

Assign/Unassign an Issue

Action

In Make“Assigns an issue to a user.”

Gives an issue an owner, or removes the current one, so no ticket sits in the queue without someone responsible for it.

When to use it
for routing rules, such as sending billing bugs to the finance developer as soon as they are created.
Watch out
a reassignment is likely to look like an update to the scheduled Watch Issues; filter so the scenario does not react to its own edits.
Jira Cloud Platform5

Create a Component

Action

In Make“Creates a component.”

Adds a component to a project, the label Jira uses to sort issues by area of the product, like checkout or mobile app.

When to use it
when a new product area or client module is declared in another tool and your Jira structure should follow.
Watch out
run List Project Components first if the same name might already exist, so you avoid near duplicates.
Jira Cloud Platform6

Create an Issue

Action

In Make“Creates a new issue.”

Opens a new ticket in the project you pick, filled with data mapped from earlier modules, so requests become work items with no copy and paste.

When to use it
when a support form, a monitoring alert or a sales handoff should land in the backlog as it arrives.
Watch out
Make lists the fields of your project once the connection exists; test with Run once to see what the issue really receives.
Jira Cloud Platform8

Create a Project Version

Action

In Make“Creates a project version.”

Adds a version to a project, the release bucket Jira uses to group issues that ship together.

When to use it
when your release plan lives in another tool, such as a roadmap sheet, and each new release there should exist in Jira too.
Watch out
check List Project Versions first if the scenario might run twice on the same release name.
Jira Cloud Platform9

Create Custom Fields Options

Action

In Make“Creates options for a custom select field.”

Adds new choices to a custom select field, so a dropdown in Jira grows with your business instead of waiting for an admin.

When to use it
when a new client or product appears in your CRM and should become a selectable value on tickets.
Watch out
this works on select fields only; read the current list with Get All Custom Field Options before adding, to avoid duplicates.
Jira Cloud Platform10

Delete a Component

Action

In Make“Deletes a Component.”

Removes a component from a project, which keeps the list short when a product area is retired.

When to use it
as part of a cleanup flow triggered when a module is marked as discontinued in your product catalog.
Watch out
Make has no undo for it, so test with Run once on a dummy component before switching the scenario on.
Jira Cloud Platform11

Delete an Attachment

Action

In Make“Deletes an attachment.”

Removes a file from a ticket, useful when documents should not stay in Jira once they have been processed elsewhere.

When to use it
after Download an Attachment has copied a sensitive file to secure storage, to leave no copy on the issue.
Watch out
treat the deletion as final and make sure the copy succeeded earlier in the same scenario.
Jira Cloud Platform12

Delete an Issue

Action

In Make“Deletes an issue.”

Erases a ticket completely, for test issues, spam from a public form or duplicates that should leave no trace.

When to use it
when a filter step has already confirmed the issue is junk, for example a form submission that failed validation.
Watch out
a deleted issue does not come back, so prefer a status change with Update an Issue Status when history might matter.
Jira Cloud Platform13

Delete an Issue Comment

Action

In Make“Deletes a commnet on a specific issue.”

Takes one comment off an issue while leaving the ticket and its other comments in place.

When to use it
to remove an automated note that has become outdated, such as a status message your scenario posted earlier.
Watch out
you need the exact comment, so pair it with List Issue Comments and a filter that picks the right one.
Jira Cloud Platform15

Delete a Project Version

Action

In Make“Deletes a project version.”

Removes a release from a project, handy when a planned version is dropped and should vanish from the release list.

When to use it
when your roadmap tool marks a release as abandoned and Jira should mirror that choice.
Watch out
look at the issues of that version with Search Issues first, so nothing still planned loses its release.
Jira Cloud Platform16

Delete a Watcher from an Issue

Action

In Make“Deletes a user as a watcher of an issue.”

Stops a person from receiving updates on a ticket, which trims noisy notifications once their part is done.

When to use it
when someone leaves a client account or a team, and their subscriptions on open issues should end.
Watch out
run List Issue Watchers first to confirm the person is on the list, otherwise the step has nothing to remove.
Jira Cloud Platform17

Delete Custom Field Option

Action

In Make“Deletes a custom field option.”

Takes a value out of a custom select field, so obsolete clients or products stop appearing in the dropdown.

When to use it
when a contract ends in your CRM and that client should no longer be selectable on new tickets.
Watch out
removal is permanent; read the current options with Get All Custom Field Options to target the right one.
Jira Cloud Platform18

Download an Attachment

Action

In Make“Downloads an attachment.”

Fetches a file stored on a ticket and passes it to the next module, ready to be saved, shared or read by another app.

When to use it
to archive signed documents in your cloud storage, or to send a screenshot to a vendor.
Watch out
files count toward your data transfer, which is 512 MB on the Free plan, and each file there is capped at 5 MB.
Jira Cloud Platform19

Get an Issue

Action

In Make“Returns the details for an issue.”

Reads every detail of one issue you already know, so later modules can use its full content.

When to use it
after the instant trigger, when the event tells you which ticket moved but you need its full content for a message.
Watch out
it returns one issue only; to find tickets by criteria, reach for Search Issues instead.
Jira Cloud Platform20

Get an Issue Comment

Action

In Make“Returns an issue comment.”

Retrieves a single comment from an issue so you can forward or analyze that exact message.

When to use it
when a scenario already knows which comment matters, for instance one flagged by a previous step, and must copy it to a customer thread.
Watch out
if you do not know the comment yet, List Issue Comments is the right starting point.
Jira Cloud Platform21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Jira Cloud Platform API with your existing connection, covering what the 40 ready modules leave out.

When to use it
when you need an operation that no module offers, and the Jira API documentation shows the endpoint for it.
Watch out
you write the request yourself, so keep the Jira Cloud Platform API documentation open to check the path and method.
Jira Cloud Platform22

Reorder Custom Fields Options

Action

In Make“Changes the order of custom field options or cascading options in a context.”

Changes the order in which choices appear in a custom select field, including cascading options, so the most used values sit on top.

When to use it
after adding new options automatically, to keep the dropdown sorted the way your team expects.
Watch out
it works inside one field context, so identify the right field before mapping the new order.
Jira Cloud Platform23

Update a Component

Action

In Make“Updates a component.”

Edits an existing component, so Jira keeps pace with how your product is organized.

When to use it
when a product area is renamed in your catalog and the matching component should follow without manual edits.
Watch out
find the component with List Project Components first; a wrong match edits a component your team still uses.
Jira Cloud Platform24

Update an Issue

Action

In Make“Updates an existing issue.”

Changes the content of an existing ticket, with values coming from another app.

When to use it
when a customer upgrades their plan in your CRM and the matching Jira tickets should say so.
Watch out
to move the ticket to another status, the dedicated module is Update an Issue Status (Transition Issue).
Jira Cloud Platform25

Update an Issue Comment

Action

In Make“Updates a comment to a specific issue.”

Rewrites a comment already posted on an issue, so an automated progress note stays current instead of piling up new ones.

When to use it
for a single status comment your scenario refreshes whenever a build or a shipment moves forward.
Watch out
keep the comment reference from Add an Issue Comment, or find it again with List Issue Comments.
Jira Cloud Platform26

Update an Issue Status (Transition Issue)

Action

In Make“Updates an issue status.”

Moves a ticket through your workflow, from To Do to In Progress or Done, as if someone had dragged it on the board.

When to use it
when a merged pull request or a paid invoice should close the matching ticket automatically.
Watch out
only transitions allowed from the current status work; List Current Available Transitions in an Issue tells you which ones.
Jira Cloud Platform27

Update a Project Version

Action

In Make“Updates a project version.”

Changes an existing release, so Jira matches the plan the team actually follows.

When to use it
when a release date or scope changes in your roadmap tool and product managers should not update Jira twice.
Watch out
locate the version with List Project Versions before editing, especially when names look alike.
Jira Cloud Platform28

Update Custom Fields Options

Action

In Make“Updates the options of a custom field.”

Edits values that already exist in a custom select field, which fixes a typo or a renamed client everywhere the option is used.

When to use it
when a client changes its company name in your CRM and tickets should show the new label.
Watch out
target the option through Get All Custom Field Options, rather than creating a second option next to the old one.
Jira Cloud Platform29

Get All Custom Field Options

Search

In Make“Returns a list of all the options of a select list issue field.”

Lists every choice of a select list field, each one as its own bundle, so you can compare Jira with another source.

When to use it
before creating, updating or deleting options, to check what already exists and avoid duplicates.
Watch out
like every search module, it can return zero, one or many bundles, and each module after it runs once per bundle.
Jira Cloud Platform30

Get Changelog of an Issue

Search

In Make“Retrieves changelog of an issue.”

Retrieves the history of an issue, meaning who changed what and when, so you can audit or report on a ticket's life.

When to use it
to measure how a critical incident moved between statuses, or to prove who closed a ticket.
Watch out
a long history returns many bundles; add an aggregator if you want one summary instead of one line per change.
Jira Cloud Platform31

List Current Available Transitions in an Issue

Search

In Make“Lists current available transitions in an issue.”

Shows which moves the workflow allows for a ticket right now, so the scenario never tries a status change Jira will refuse.

When to use it
just before Update an Issue Status (Transition Issue), especially when projects use different workflows.
Watch out
the list depends on the issue's current status, so read it again if an earlier step already moved the ticket.
Jira Cloud Platform32

List Issue Comments

Search

In Make“Returns all comments for an issue.”

Returns all the comments on an issue as separate bundles, ready to be filtered, forwarded or summarized.

When to use it
to copy the discussion of a closed ticket into a customer report, or to find one comment to edit or delete.
Watch out
busy tickets produce many bundles, and each later module spends one operation per comment.
Jira Cloud Platform33

List Issue Watchers

Search

In Make“Returns the watchers for an issue.”

Gives you everyone following a ticket, so you can notify them elsewhere or clean up the list.

When to use it
to send the watchers of an escalated issue a direct message in your chat tool, beyond Jira's own emails.
Watch out
a ticket with no watchers returns nothing, and the modules after it simply do not run.
Jira Cloud Platform34

List Project Components

Search

In Make“Retrieves project components.”

Retrieves the components of a project, so your scenario knows which product areas exist before it creates or routes anything.

When to use it
to sync the list of areas with a documentation site, or to check a name before Create a Component.
Watch out
each component becomes a bundle, so later steps repeat once per component unless you aggregate them.
Jira Cloud Platform35

List Project Versions

Search

In Make“Retrieves all versions in a project.”

Returns all the versions of a project, released or not, which gives your scenario the full release calendar to work from.

When to use it
to publish upcoming releases on a status page, or to find the version you want to update or delete.
Watch out
older projects can hold many versions; filter them before sending anything outside Jira.
Jira Cloud Platform36

List Users

Search

In Make“Retrieves all users (active and inactive).”

Retrieves every user of your Jira site, active and inactive, which is the base for access reviews and directory syncs.

When to use it
to compare Jira accounts with your HR tool and spot people who left but still hold a seat.
Watch out
inactive users come back too, so add a filter when you only care about current accounts; for one person, Search Users is lighter.
Jira Cloud Platform37

Search Issues

Search

In Make“Searches for issues.”

Finds the tickets that match your criteria and returns each one as a bundle, the way you would filter the issue list in Jira.

When to use it
to gather every open bug of a release for a report, or to check whether a ticket already exists before creating one.
Watch out
zero results means the next modules skip, while many results multiply the operations spent.
Jira Cloud Platform38

Search Users

Search

In Make“Searches for users by query.”

Looks up people by a query, such as part of a name or an email, and returns the matching Jira accounts.

When to use it
before Assign/Unassign an Issue or Add a Watcher, when the other app only gives you a name.
Watch out
a vague query can match several people; add a filter so the scenario picks exactly one before assigning.
Need help

Need help automating Jira Cloud Platform with Make?

A person reads every message.

FAQ

Questions about the Jira Cloud Platform Make integration

01Is the Jira Cloud Platform Make integration free?
Yes, Jira Cloud Platform is a standard app, so it works on the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle, so busy search modules weigh on your monthly allowance.
02What do you need to connect Jira Cloud Platform to Make?
You need three things: the Service URL of your Jira site, your Username, and an API token created at id.atlassian.com. The token is generated from the API tokens page with a label of your choice, and it is shown only once, so copy it before closing the window. In Make, click Add next to the Connection field of any Jira module, fill the three fields and click Save. The same connection then serves all 40 modules.
03Does the Jira Cloud Platform trigger in Make work in real time?
It depends on which Watch Issues you pick. The instant version reacts as soon as a ticket event occurs, because Jira calls Make through a webhook; it needs an account with the Administer Jira global permission, and an instance holds up to 100 active admin webhooks. The scheduled version checks for created or updated issues on the scenario's schedule, every 15 minutes by default, with 1 minute possible on paid plans.
04What if a Jira Cloud Platform module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Jira Cloud Platform API with the connection you already set up, so you are not limited to the 28 actions and 10 searches. The Jira Cloud Platform API documentation lists the available endpoints. If your blocker is the webhook quota of the instant trigger, the scheduled Watch Issues is the alternative, since it does not rely on a webhook.
05Should you use Make or n8n for Jira Cloud Platform?
It depends on the criteria that matter to your team. On Make, Jira Cloud Platform comes with 40 modules, including an instant and a scheduled trigger, plus Make an API Call for the rest of the API, and it runs on every plan. n8n may also offer a Jira node, so compare the operations each tool covers for your use case, how each one counts usage, and which editor your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations