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

1

Create an API token

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

2

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.

3

Run your first script

Fork any script below and read a project before writing anything. There are hundreds here, so search by the verb you need.

Scripts

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

Resource type

jira — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
domainstringYes
passwordstringYes
usernamestringYes

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. There are no per-token scopes, so create the token on an account with only the project access the scripts need.

Is my token stored on the hub?

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