Jira Data Center Trigger icon

Jira Data Center Trigger

Handle Jira Data Center webhooks

Jira Data Center Trigger

AI-generated

Overview

This node acts as a trigger for Jira Data Center webhooks, allowing workflows to start when specific Jira events occur. It listens for various Jira events such as issue creation, updates, deletions, comments, project changes, version releases, and user modifications. This is particularly useful for automating processes that depend on real-time Jira activity, like syncing issues with other tools, notifying teams about changes, or updating external databases.

For example, you could use this node to:

  • Trigger a workflow whenever a new issue is created in Jira to automatically assign it or notify a team.
  • Start a process when an issue transitions status to update related records elsewhere.
  • React to comment additions by sending alerts or logging feedback.

Properties

Name Meaning
Authentication Method used to authenticate with Jira Data Center: either "Personal Access Token" or "Basic Auth".
Project (Optional) Filter events to a specific Jira project by its key. Leave empty to listen to all projects.
Events The Jira events to listen to. Multiple options include:
- Issue Created, Issue Updated, Issue Deleted, Issue Assigned, Issue Transitioned
- Comment Created, Comment Updated, Comment Deleted
- Project Created, Project Updated, Project Deleted
- Version Created, Version Updated, Version Released, Version Deleted
- User Created, User Updated, User Deleted

Output

The node outputs JSON data representing the webhook event received from Jira. The structure includes:

  • event: The event type string (e.g., "jira:issue_created").
  • timestamp: Timestamp of the event or current time if not provided.
  • headers: HTTP headers from the webhook request.
  • body: The full webhook payload.
  • Depending on the event type, additional fields may be included:
    • For issue-related events: issue, user, changelog.
    • For comment events: comment, issue, user.
    • For project events: project, user.
    • For version events: version, project, user.
    • For user events: user.

The output is always an array of such event objects wrapped in the standard n8n JSON format.

No binary data output is produced by this node.

Dependencies

  • Requires access to a Jira Data Center instance with webhook support.
  • Needs credentials for authentication, either via a personal access token or basic authentication.
  • The node dynamically creates and deletes webhooks on the Jira server to receive events.
  • Requires proper configuration of the webhook URL accessible by Jira Data Center.

Troubleshooting

  • Webhook creation failure: If the webhook cannot be created on Jira endpoints, check network accessibility and credentials. Localhost URLs will warn but allow manual testing.
  • Event filtering: If no workflow triggers occur, verify that the selected events and optional project filter match the incoming webhook payload.
  • Authentication errors: Ensure the API token or basic auth credentials are valid and have sufficient permissions.
  • Unexpected payloads: The node expects requests from Jira Data Center identified by the "user-agent" header containing "atlassian". Requests missing this will be rejected.
  • Webhook deletion warnings: Failures deleting webhooks are logged but do not stop workflow execution; manual cleanup might be needed.

Links and References

Discussion