JIRA n8n INTEGRATION: AUTOMATE JIRA WITH N8N

This action retrieves detailed information about a specific Jira user, including their display name, email, account status, and avatar URL. It's essential for workflows that need to personalize communications or validate user data.

Key parameters:

• Credential to connect with (dropdown, required): Select your configured Jira account credentials
• Account ID (text field, optional): The unique identifier of the Jira user to retrieve. You can find this in Jira's user profile URL or from previous workflow outputs

Use cases:

• Fetch user details before sending personalized email notifications
• Validate that an assignee exists before creating or updating issues
• Build a user directory by combining with "Get Many" operations

This action permanently removes a user from your Jira instance. Use it with caution—this operation cannot be undone and will remove all user associations.

Key parameters:

• Credential to connect with (dropdown, required): Your Jira authentication credentials
• Account ID (text field, required): The unique identifier of the user account to delete

Use cases:

• Automate offboarding workflows when employees leave your organization
• Clean up test accounts after QA cycles
• Sync user deletions from your HR system (Workday, BambooHR) to Jira

This action provisions a new user in your Jira instance with specified credentials and profile information. It's particularly valuable for onboarding automation.

Key parameters:

• Username (text field, required): The unique username for the new Jira user
• Email Address (text field, required): The user's email for notifications and password recovery
• Display Name (text field, required): The full name shown in Jira's interface
• Additional Fields: Optional properties like locale, notification preferences, or group memberships

Use cases:

• Automatically create Jira accounts when new employees are added to your HR system
• Provision users based on form submissions (Typeform, Google Forms)
• Sync user creation from your identity provider (Okta, Azure AD)

This action modifies an existing comment on a Jira issue, allowing you to correct information, add updates, or append additional context programmatically.

Key parameters:

• Issue Key (text field, required): The unique identifier of the issue (e.g., "PROJECT-123")
• Comment ID (text field, required): The specific ID of the comment to update
• Comment (text field, required): The new content that will replace the existing comment
• JSON Parameters (toggle): Enable to pass complex formatting via raw JSON

Use cases:

• Automatically update comments with resolution details when issues are closed
• Append timestamps or status changes to existing comments for audit trails
• Correct automated comments that contained outdated information

This action deletes a specific comment from a Jira issue. It's useful for cleaning up automated comments or removing outdated information.

Key parameters:

• Issue Key (text field, required): The issue identifier containing the comment
• Comment ID (text field, required): The unique ID of the comment to remove

Use cases:

• Clean up temporary or draft comments from automated processes
• Remove outdated status update comments after issue resolution
• Delete duplicate comments created by integration errors

This action retrieves multiple comments from a specified Jira issue, with options to limit results or fetch all comments. Perfect for reporting and analysis workflows.

Key parameters:

• Issue Key (text field, optional): The issue to fetch comments from
• Return All (toggle): When enabled, retrieves all comments without limit
• Limit (number field): Maximum comments to return (default: 50)

Use cases:

• Generate comment summaries for weekly reports
• Export issue discussions to external documentation tools
• Analyze comment patterns for workflow optimization

This action retrieves a single, specific comment from a Jira issue using its unique identifier. Use it when you need precise comment data rather than a full list.

Key parameters:

• Issue Key (text field, required): The parent issue identifier
• Comment ID (text field, required): The specific comment to retrieve

Use cases:

• Fetch comment details to verify content before taking action
• Retrieve comments referenced by webhooks for further processing
• Validate comment existence before attempting updates

This action creates a new comment on a specified Jira issue. It's one of the most commonly used actions for keeping stakeholders informed automatically.

Key parameters:

• Issue Key (text field, required): The issue to comment on (e.g., "DEV-456")
• Comment (text area, required): The comment content (supports Jira markup)
• JSON Parameters (toggle): Enable for advanced formatting options

Use cases:

• Automatically log external communications (emails, Slack messages) as issue comments
• Add status update comments when issues move through workflow stages
• Post automated test results or deployment notifications directly on issues

This action deletes a specific attachment from your Jira instance. Note that you need the attachment ID, not the issue key.

Key parameters:

• Attachment ID (text field, required): The unique identifier of the attachment to delete

Use cases:

• Clean up outdated or superseded attachments
• Remove sensitive files after they've been processed
• Automate attachment lifecycle management

This action retrieves multiple attachments from a specified Jira issue, allowing you to list all files associated with a ticket.

Key parameters:

• Issue Key (text field, required): The issue to fetch attachments from
• Return All (toggle): Fetch all attachments without limit
• Limit (number field): Maximum attachments to return (default: 50)
• Download (toggle): Download attachment content as binary data

Use cases:

• Archive all issue attachments to cloud storage like AWS S3 when tickets close
• Generate attachment inventories for compliance audits
• Sync attachments to external document management systems

This action retrieves a single attachment's metadata or content from Jira using its unique attachment ID.

Key parameters:

• Attachment ID (text field, required): The unique identifier of the attachment
• Download (toggle): When enabled, downloads the actual file content

Use cases:

• Fetch specific attachments for processing or transformation
• Verify attachment existence before referencing in other systems
• Download files for virus scanning or content analysis

This action uploads a file to a Jira issue as an attachment. The file must be provided as binary data from a previous node in your workflow.

Key parameters:

• Issue Key (text field, required): The issue to attach the file to
• Input Binary Field (text field, required): The name of the binary data field containing the file (default: "data")

Use cases:

• Automatically attach screenshots from error monitoring tools (Sentry, Bugsnag)
• Add generated reports (PDFs, spreadsheets) to relevant issues
• Sync attachments from email or other ticketing systems

This action modifies an existing Jira issue's fields. You can update any field you have permission to change, including custom fields.

Key parameters:

• Issue Key (text field, required): The issue to update (e.g., "PROJ-789")
• Update Fields (dynamic): Add specific fields to update (summary, description, assignee, priority, custom fields, etc.)

Use cases:

• Automatically update issue status when external conditions change
• Sync field values from CRM or sales tools
• Bulk update issues based on business rules or schedules

This action retrieves the current status of a specified Jira issue, including available transitions. Useful for workflows that need to make decisions based on issue state.

Key parameters:

• Issue Key (text field, required): The issue to check status for
• Additional Fields: Optional parameters to include transition information

Use cases:

• Route workflows differently based on current issue status
• Validate status before attempting transitions
• Build status dashboards pulling real-time data

This action sends notifications about a Jira issue to specified recipients. It's perfect for alerting stakeholders who might not be watching the issue directly.

Key parameters:

• Issue Key (text field, required): The issue to notify about
• Notification Recipients: Specify users, groups, or roles to notify
• Notification Recipients Restrictions: Limit who can receive the notification
• Additional Fields: Customize notification content

Use cases:

• Alert managers when critical issues are created
• Notify external stakeholders about issue updates
• Send deadline reminders for upcoming due dates

This action retrieves multiple issues from Jira based on your criteria. Use JQL (Jira Query Language) via options to filter results precisely.

Key parameters:

• Return All (toggle): Fetch all matching issues
• Limit (number field): Maximum issues to return (default: 50)
• Options: Additional filtering and sorting parameters

Use cases:

• Generate daily reports of all issues updated in the last 24 hours
• Sync issue data to external databases or spreadsheets
• Build custom dashboards with filtered issue lists

This action retrieves complete details for a single Jira issue. It returns all fields, comments, attachments, and metadata associated with the issue.

Key parameters:

• Issue Key (text field, required): The issue to retrieve (e.g., "TEAM-123")
• Simplify (toggle): Return simplified data structure for easier processing
• Additional Fields: Include specific expanded data

Use cases:

• Fetch full issue context before making automated decisions
• Populate templates or notifications with issue details
• Validate issue data before performing updates

This action permanently deletes a Jira issue. This cannot be undone—the issue and all associated data will be removed.

Key parameters:

• Issue Key (text field, required): The issue to delete
• Delete Subtasks (toggle): When enabled, also deletes all subtasks of the issue

Use cases:

• Clean up test issues after QA cycles
• Automate deletion of spam or duplicate issues
• Remove issues created by integration errors

This action creates a new Jira issue with specified fields. It's essential for any workflow that needs to generate tickets automatically.

Key parameters:

• Project (dropdown/text, required): The Jira project to create the issue in
• Issue Type (dropdown/text, required): The type of issue (Bug, Task, Story, etc.)
• Summary (text field, required): The issue title
• Additional Fields: Description, assignee, priority, labels, custom fields, and more

Use cases:

• Automatically create issues from customer support requests
• Generate bug reports from error monitoring tools
• Create tasks from form submissions or email requests
• Sync issues from other project management tools like Asana or ClickUp

This action retrieves the complete change history for a Jira issue, showing who changed what and when. Invaluable for auditing and reporting.

Key parameters:

• Issue Key (text field, required): The issue to fetch changelog for
• Return All (toggle): Retrieve complete history
• Limit (number field): Maximum entries to return (default: 50)

Use cases:

• Generate audit reports showing all issue modifications
• Track time spent in each status for cycle time analysis
• Identify patterns in issue changes for process improvement