- Integrations
- /
- Jira
- /
- with Discord
Discord + Jira: surface engineering work into community channels.
Post Jira issue events into Discord channels for open-source projects, community contributors, or async-first engineering teams.
Workflows fire when something happens in Jira.
- Comment CreatedWebhook
- New IssueWebhook
- Issue DeletedWebhook
- Issue UpdatedWebhook
- Sprint ClosedWebhook
Workflows do something in Discord, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Jira, do it in Discord.
6 Jira triggers wired to 8 Discord actions. Most-used pairing: Comment Created → Add Reaction.
Or fire it the other way around.
3 Discord triggers wired to 17 Jira actions downstream.
See Discord → Jira →Common Jira → Discord workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.
Connect Jira and Discord in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Jira and Discord
Open Tiny Command, authorize Jira and Discord once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Jira trigger
Drop the Jira → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/jira.trigger-comment-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Discord action
Drop the Discord → Add Reaction action below it. Map fields from the Jira payload into the Discord inputs.
discord.add-reaction - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Jira + Discord.
When does Discord + Jira make sense?
How do I post new Jira issues to Discord?
Can I post Jira sprint kickoffs to Discord?
How do I create Jira issues from Discord messages?
Can I post Jira PR/issue status changes to Discord?
How do I avoid spamming Discord on minor Jira edits?
Other apps that pair well with Jira.
Wire Jira to Discord in 2 minutes.
Free tier available. No credit card. No onboarding call.