Jira

Project Management integration · 26 node(s) including 1 trigger.

00Overview

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Jira

Add your credentials as a Flomation environment secret, then pick them in each node. The connection fields are:

Field	Type		Details
API Token	`secret`	Required	id.atlassian.com ▸ Security ▸ Create and manage API tokens

Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.

02Attachment

Add Attachment

jira/attachment_add · Action

Attach a file to a Jira issue. Provide the issue key, a file name (e.g. report.pdf) and the file's bytes as base64 — Flomation uploads it to the issue. Returns the created attachment's details.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to attach the file to, e.g. SCRUM-1
File Name	`string`	Required	The name to store the file under, e.g. report.pdf
File Content (base64)	`string`	Required	The file's bytes, base64-encoded

Returns: id, result, tool_result, success, error

Get Attachment

jira/attachment_get · Action

Fetch a Jira attachment's details by its ID. Optionally download the file itself — when Download File is on, the file's bytes are returned base64-encoded on the File Content output.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Attachment ID	`string`	Required	The attachment's numeric ID, e.g. 10001
Download File	`boolean`		Also download the file's bytes (returned base64-encoded)

Returns: id, result, base64_content, tool_result, success, error

Get Many Attachments

jira/attachment_get_all · Action

List every attachment on a Jira issue. Provide the issue key; the attachments are read from the issue itself. Turn on Return All to get them all, or set a Limit to cap how many are returned.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to read attachments from, e.g. SCRUM-1
Return All	`boolean`		Return every attachment on the issue
Limit	`integer`		Maximum number to return when Return All is off

Returns: results, count, total, tool_result, success, error

Delete Attachment

jira/attachment_remove · Action

Permanently delete a Jira attachment by its ID. This removes the file from its issue and cannot be undone.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Attachment ID	`string`	Required	The attachment's numeric ID, e.g. 10001

Returns: id, result, tool_result, success, error

03Comment

Add Comment

jira/comment_add · Action

Add a comment to a Jira issue. Enter the issue key (e.g. SCRUM-1) and the comment text — it is posted as a plain-text comment on the issue.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to comment on, e.g. SCRUM-1
Comment	`text`	Required	The comment text (plain text)

Returns: id, result, tool_result, success, error

Get Comment

jira/comment_get · Action

Fetch a single comment from a Jira issue by its ID. Enter the issue key (e.g. SCRUM-1) and the comment ID to return the full comment.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the comment belongs to, e.g. SCRUM-1
Comment ID	`string`	Required	The ID of the comment to fetch

Returns: id, result, tool_result, success, error

Get Many Comments

jira/comment_get_all · Action

List the comments on a Jira issue. Enter the issue key (e.g. SCRUM-1) and either return everything or cap the number returned. Optionally order by newest or oldest first.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to list comments for, e.g. SCRUM-1
Return All	`boolean`		Return every comment (ignores Limit)
Limit	`integer`		Maximum number of comments to return (1-100)
Order By	`string`		Sort order for the comments — choices: Newest first, Oldest first

Returns: results, count, total, tool_result, success, error

Delete Comment

jira/comment_remove · Action

Permanently delete a comment from a Jira issue. Enter the issue key (e.g. SCRUM-1) and the comment ID to remove. This cannot be undone.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the comment belongs to, e.g. SCRUM-1
Comment ID	`string`	Required	The ID of the comment to delete

Returns: id, result, tool_result, success, error

Update Comment

jira/comment_update · Action

Change the text of an existing comment on a Jira issue. Enter the issue key (e.g. SCRUM-1), the comment ID, and the new comment text.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the comment belongs to, e.g. SCRUM-1
Comment ID	`string`	Required	The ID of the comment to update
Comment	`text`	Required	The new comment text (plain text)

Returns: id, result, tool_result, success, error

04Issue

Get Issue Changelog

jira/issue_changelog · Action

Retrieve the full change history of a Jira issue — every field edit, status move and assignment, in order. Return all history entries, or cap them to a limit.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key, e.g. SCRUM-1
Return All	`boolean`		Fetch every history entry
Limit	`integer`		Maximum entries to return when not returning all

Returns: results, count, total, tool_result, success, error

Create Issue

jira/issue_create · Action

Create a Jira issue. Pick the project and issue type, set a summary and description, and optionally assign it, set a priority, add labels or link a parent (for subtasks). Any other field can be set via Custom Fields or Additional Fields.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Project	`string`	Required · ● live picker	Choose a project
Issue Type	`string`	Required · ● live picker	Choose an issue type
Summary	`string`	Required	A short one-line title for the issue
Description	`text`		The issue description (plain text)
Priority	`string`	● live picker	Choose a priority
Assignee	`string`	● live picker	Choose a user to assign
Reporter	`string`	● live picker	Choose the reporting user (defaults to you)
Labels	`string`		Comma-separated labels, e.g. backend,urgent
Component IDs	`string`		Comma-separated component IDs
Parent Issue Key	`string`		Required for a subtask — the parent issue key, e.g. SCRUM-12
Due Date	`string`		YYYY-MM-DD
Custom Fields (JSON)	`object`		{"customfield_10011":"value"}
Additional Fields (JSON)	`object`		{"environment":"production"}

Returns: id, result, tool_result, success, error

Delete Issue

jira/issue_delete · Action

Permanently delete a Jira issue by its key. Optionally delete the issue's subtasks along with it. This cannot be undone.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key to delete, e.g. SCRUM-1
Delete Subtasks	`boolean`		Also delete the issue's subtasks

Returns: id, result, tool_result, success, error

Get Issue

jira/issue_get · Action

Fetch a single Jira issue by its key. Optionally narrow the returned data to specific fields, or expand extra sections such as the changelog or rendered fields.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key, e.g. SCRUM-1
Fields	`string`		Comma-separated fields to return, e.g. summary,status,assignee
Expand	`string`		Comma-separated sections to expand, e.g. changelog,renderedFields

Returns: id, result, tool_result, success, error

Search Issues

jira/issue_get_all · Action

Search Jira issues using a JQL query. Leave the query blank to list every issue, or narrow the search and choose which fields to return. Return everything, or cap the results to a limit.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
JQL Query	`text`		e.g. project = SCRUM AND status = "In Progress" ORDER BY created DESC
Fields	`string`		Comma-separated fields to return, e.g. summary,status,assignee
Expand	`string`		Comma-separated sections to expand, e.g. changelog,renderedFields
Return All	`boolean`		Fetch every matching issue
Limit	`integer`		Maximum issues to return when not returning all

Returns: results, count, total, tool_result, success, error

Notify About Issue

jira/issue_notify · Action

Send an email notification about a Jira issue. Set a subject and message body, and choose who receives it — the reporter, assignee, watchers, voters, or named users and groups.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key, e.g. SCRUM-1
Subject	`string`		The email subject line
Text Body	`text`		The plain-text message body
HTML Body	`text`		The HTML message body
Notify Reporter	`boolean`		Email the issue reporter
Notify Assignee	`boolean`		Email the issue assignee
Notify Watchers	`boolean`		Email everyone watching the issue
Notify Voters	`boolean`		Email everyone who voted on the issue
To Users	`string`		Comma-separated account IDs to notify
To Groups	`string`		Comma-separated group names to notify

Returns: id, result, tool_result, success, error

List Transitions

jira/issue_transitions · Action

List the status transitions currently available for a Jira issue — the moves it can make from its current status. Use a transition's ID with Update Issue to change the status.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key, e.g. SCRUM-1

Returns: results, count, total, tool_result, success, error

Update Issue

jira/issue_update · Action

Update an existing Jira issue. Change any of the standard fields, and optionally move the issue to a new status by choosing a transition. Leave a field blank to leave it unchanged.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue key to update, e.g. SCRUM-1
Summary	`string`		A short one-line title for the issue
Description	`text`		The issue description (plain text)
Priority	`string`	● live picker	Choose a priority
Assignee	`string`	● live picker	Choose a user to assign
Reporter	`string`	● live picker	Choose the reporting user
Labels	`string`		Comma-separated labels, e.g. backend,urgent
Component IDs	`string`		Comma-separated component IDs
Due Date	`string`		YYYY-MM-DD
Status Transition	`string`	● live picker	Choose a transition to move the issue's status
Custom Fields (JSON)	`object`		{"customfield_10011":"value"}
Additional Fields (JSON)	`object`		{"environment":"production"}

Returns: id, result, tool_result, success, error

05User

Create User

jira/user_create · Action

Invite a new user to your Atlassian site by email address. Optionally set a display name and choose which products to grant access to (leave products empty to invite the user to every product). Requires organisation-admin permission on the site.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Email Address	`string`	Required	The email address of the user to invite
Display Name	`string`		The name shown for the user, e.g. Jane Doe
Products	`string`		Comma-separated product keys (e.g. jira-software,jira-servicedesk). Leave empty to invite to all products.
Additional Fields (JSON)	`object`		{"key":"value"}

Returns: id, result, tool_result, success, error

Delete User

jira/user_delete · Action

Remove a user from your Atlassian site by their account ID. This deletes the user from the site — requires organisation-admin permission.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Account ID	`string`	Required · ● live picker	The account ID of the user to delete

Returns: id, result, tool_result, success, error

Get User

jira/user_get · Action

Look up a single Atlassian user by their account ID and return their profile. Optionally expand extra details (e.g. groups, applicationRoles) via the Expand field.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Account ID	`string`	Required · ● live picker	The account ID of the user to retrieve
Expand	`string`		Comma-separated extra details, e.g. groups,applicationRoles

Returns: id, result, tool_result, success, error

06Worklog

Add Worklog

jira/worklog_add · Action

Log time spent on a Jira issue. Give the issue key and how long was spent (e.g. "1h 30m"), optionally add a comment and set when the work started. Returns the new worklog entry.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to log time against, e.g. SCRUM-1
Time Spent	`string`	Required	How long was spent, e.g. 1h 30m
Comment	`text`		Optional note describing the work (plain text)
Started	`string`		When work started, e.g. 2026-07-06T09:00:00.000+0000
Additional Fields (JSON)	`object`		{"visibility":{"type":"group","value":"jira-developers"}}

Returns: id, result, tool_result, success, error

Delete Worklog

jira/worklog_delete · Action

Remove a worklog entry from a Jira issue by its issue key and worklog ID. This permanently deletes the logged time and cannot be undone.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the worklog belongs to, e.g. SCRUM-1
Worklog ID	`string`	Required	The ID of the worklog entry to delete

Returns: id, result, tool_result, success, error

Get Worklog

jira/worklog_get · Action

Fetch a single worklog entry from a Jira issue by its issue key and worklog ID. Returns the full worklog, including who logged it, the time spent and any comment.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the worklog belongs to, e.g. SCRUM-1
Worklog ID	`string`	Required	The ID of the worklog entry to fetch

Returns: id, result, tool_result, success, error

Get Many Worklogs

jira/worklog_get_all · Action

List the worklog entries logged against a Jira issue. Return every entry, or cap the count with a limit. Each entry includes who logged it, the time spent and any comment.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue to list worklogs for, e.g. SCRUM-1
Return All	`boolean`		Return every worklog rather than a single page
Limit	`integer`		Max worklogs to return when not returning all (default 50, max 100)

Returns: results, count, total, tool_result, success, error

Update Worklog

jira/worklog_update · Action

Change an existing worklog entry on a Jira issue. Update the time spent, the comment or when the work started — supply only the fields you want to change. Returns the updated worklog.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Issue Key	`string`	Required	The issue the worklog belongs to, e.g. SCRUM-1
Worklog ID	`string`	Required	The ID of the worklog entry to update
Time Spent	`string`		New time spent, e.g. 2h
Comment	`text`		New comment (plain text)
Started	`string`		When work started, e.g. 2026-07-06T09:00:00.000+0000
Additional Fields (JSON)	`object`		{"visibility":{"type":"group","value":"jira-developers"}}

Returns: id, result, tool_result, success, error

07Triggers

Jira Webhook Trigger

trigger/jira_webhook · Trigger

Triggers a flow when a Jira issue or comment event occurs (created, updated or deleted). The webhook is registered automatically; optionally filter with JQL, and set a signing secret to have Jira's HMAC-SHA256 payload signature verified.

Field	Type		Details
Site URL	`string`	Required	https://your-domain.atlassian.net
Account Email	`string`	Required	The Atlassian account email that owns the API token
Events	`multi_select`	Required	choices: Created, Updated, Deleted, Created, Updated, Deleted, Created, Updated, Deleted, Created, Deleted, Created, Updated, Deleted, Released, Unreleased, Moved, Created, Updated, Deleted, Started, Closed, Created, Updated, Deleted, Configuration Changed, Created, Updated, Deleted, Created, Updated, Deleted, Voting Changed, Watching Changed, Unassigned Issues Changed, Subtasks Changed, Attachments Changed, Issue Links Changed, Time Tracking Changed
JQL Filter	`string`		Optional — only fire for issues matching this JQL, e.g. project = SCRUM AND priority = High
Signing Secret	`secret`		Optional — HMAC-SHA256 signing secret (less than 128 chars)

Returns: content, webhook_event, issue_key, issue_id, user, timestamp, body

08Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

Changing an issue's status can't be done by typing a status name — first run List Transitions to get the transition ID available from the issue's current status, then supply that ID when you Update Issue.
Send Notification deliberately excludes the person who triggered it, so a notification aimed only at yourself (common on a single-user or test site) will fail with "No recipients".
Inviting or removing users requires organisation-admin permission on your Atlassian site; without it those actions will be rejected even if the rest of your connection works.
Attachments are capped at 50 MB per file for both upload and download; larger files are rejected rather than truncated.
Deletions of issues, comments, worklogs and attachments are permanent and cannot be undone, so guard them behind a condition or confirmation step in your flow.
Users are identified by their Atlassian account ID (not a username or email), so User lookups and assignee fields expect that ID — use the assignee/reporter dropdowns to pick it rather than typing a name.