Jira

Project management Email and API token

Create and update issues, move them through workflows, and read projects, boards and sprints — from any Windmill script, flow or app.

Set up in 3 steps

Create an API token

At id.atlassian.com, under Security, create an API token. Copy it — it is shown only once.

Add the resource in Windmill

Open Resources, add a resource of type jira, and fill domain with your site name — the yourteam in yourteam.atlassian.net — username with your Atlassian account email, and password with the API token.

Run your first script

Fork Get Current User to check the resource, then Search Issues with JQL to read before writing anything. Projects, issue types, boards, sprints and transitions are picked from live dropdowns.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Submit a script →

Trigger flows from Jira

Jira is not only a destination. These inbound paths are supported today.

Jira webhooks on an HTTP route

Create a Windmill HTTP route, then as a Jira admin open Settings, System, WebHooks and add a webhook pointing at it. Pick the events (issue created, updated, deleted, comments, sprints) and narrow them with a JQL filter such as project = PROJ. Give the webhook a secret and set the route to Signature authentication with a Custom scheme — header X-Hub-Signature, sha256, hex, prefix sha256= — so only signed deliveries start your flow. The payload carries the full issue, so most flows need no follow-up call.

Automation rules

A Jira automation rule's Send web request action can call the same HTTP route on any rule trigger — a transition, a field change, a schedule — without admin rights on the whole site.

Resource type

The shape of the credential every script on this page expects.

jira

View raw schema →

Field	Type	Required
domain	string	Yes
password	string	Yes
username	string	Yes

Questions

Why is the token in the password field?

Jira Cloud authenticates over HTTP Basic, with your account email as the username and the API token in place of a password. Your actual Atlassian password will not work.

What goes in domain?

Just the site name. For yourteam.atlassian.net, enter yourteam — every request is built from it.

What can the token do?

Everything the account behind it can, so create the token on an account with only the project access the scripts need. Tokens expire — a year at most — so note the date and replace the password field before then.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

Set up in 3 steps

Create an API token

Add the resource in Windmill

Run your first script

Scripts

Move Issues to Sprint

List Sprints

List Sprint Issues

List Epics

List Epic Issues

List Boards

List Board Issues

Get Sprint

Get Cloud ID

Get Board

Create Future Sprint

Count Issues Using JQL

Get Current User

Create Issue

Get Task

Get Users

Get Transitions

Get Issue Picker Suggestions

Get All Projects

Assign Issue

Get Issue Types

List Issue Comments

Check Issues Against JQL

Download Attachment

Search Issues with JQL

Update Comment

Get User

Delete Project

Add Comment to Issue