- Integrations
- /
- Jira
- /
- Triggers
- /
- Comment Created
TriggerJiraReal-timeUpdated May 2026
How do I trigger when a Jira comment is added?
Short answer: Drop the "Jira → Comment Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Jira, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Comment Created
When the matching event happens
on comment createdcomment addedwhen comment createdwhen a comment is added to a jira issuenew commentwatch for comment creatednew comment created
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"event": "comment_created","summary": "Sample issue","issue_key": "PROJ-42"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| event | string | "comment_created" |
| summary | string | "Sample issue" |
| issue_key | string | "PROJ-42" |
Pairs with
Drop these actions after Comment Created.
FAQ
Questions about Comment Created.
How does the Comment Created trigger work in Jira?
Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.
Is the Comment Created trigger real-time?
Yes. Comment Created uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Jira.
What data does Comment Created return?
The full event payload from Jira. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Comment Created so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Jira admin permissions to use Comment Created?
For most Jira accounts a standard user can authorize the trigger. Some Jira plans require an admin to enable third-party webhooks. Check Jira's docs if the trigger fails to register.
More triggers
Other Jira triggers.
Trigger
New Issue
Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.
TriggerIssue Deleted
Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.
TriggerIssue Updated
Fires whenever any field on a Jira issue changes (status, assignee, priority, custom fields). Combine with a field filter to react only to the changes you care about.
TriggerSprint Closed
Fires when a sprint is closed in Jira. Use to roll up sprint metrics, generate a retrospective doc, or auto-create the next sprint.
TriggerSprint Started
Fires when a sprint is started in Jira. Useful for kicking off stand-up bots, posting sprint goals to Slack, or seeding a sprint-board template.
Build a workflow on this trigger.
One trigger. 17+ downstream actions. Zero glue.