Start free
Per-pair page

Gmail + Jira: create issues from emails, notify on changes.

Create Jira issues from labeled Gmail messages, and send Gmail notifications for Jira issue events (assigned, transitioned, commented).

Connect Jira and GmailSee reverse direction
Trigger app
Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →
Action app
Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Jira → Gmail

When something happens in Jira, do it in Gmail.

6 Jira triggers wired to 27 Gmail actions. Most-used pairing: Comment Created → Add Labels to Message.

Gmail → Jira

Or fire it the other way around.

1 Gmail triggers wired to 17 Jira actions downstream.

See Gmail → Jira →
Popular pairings

Common Jira → Gmail workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 162 combinations
When comment created in Jira, add labels to message in Gmail.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create draft in Gmail.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create label in Gmail.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, delete draft in Gmail.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When new issue in Jira, add labels to message in Gmail.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create draft in Gmail.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, create label in Gmail.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When new issue in Jira, delete draft in Gmail.

Fires when a new issue is created in Jira. The standard inbound hook for routing, enrichment, auto-labeling, and SLA-aware notifications.

When issue deleted in Jira, add labels to message in Gmail.

Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.

How it works

Connect Jira and Gmail in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Jira and Gmail

    Open Tiny Command, authorize Jira and Gmail once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick 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
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Gmail action

    Drop the Gmail → Add Labels to Message action below it. Map fields from the Jira payload into the Gmail inputs.

    google-gmail.add-labels
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Jira + Gmail.

How do I create a Jira issue from a Gmail message?
Gmail Email Received with label "@jira" → Jira Create Issue with title = email subject, body = email content + sender email. Useful for capturing internal bug reports from email.
Can I notify via Gmail when a Jira issue is assigned?
Jira covers this natively. The pair adds value when you need custom email formatting (e.g., for stakeholders without Jira), or when you want to send to a distribution list rather than just the assignee.
How do I route different Gmail labels to different Jira projects?
One workflow per Gmail label, each routing to its Jira project key. Or one workflow with a Switch node on label name. "bug-report" → BUG project, "feature-req" → PROD project.
Can I AI-classify Gmail before creating Jira issues?
Yes. Insert Claude/OpenAI step. Classify as bug, feature request, support question, spam. Only create Jira issues for bugs/features. Support questions route elsewhere; spam goes to trash.
How do I link Gmail thread to Jira issue?
Include the Gmail thread URL (https://mail.google.com/...) in the Jira issue body. After Create Issue, set a Gmail label like "filed-to-jira" so the workflow doesn't fire again.
Can I email the Gmail sender when their reported Jira issue closes?
Yes. Store the sender email on the Jira issue. On Issue Closed with "shipped" label, Gmail Send Email to the sender confirming the fix. Closes the loop with the original reporter.
Related

Other apps that pair well with Jira.

+
Jira + Slack
Communication
+
Jira + Google Sheets
Spreadsheets & Databases
+
Jira + HubSpot
CRM & Sales
+
Jira + Stripe
Payments
+
Jira + Notion
Productivity
+
Jira + Airtable
Spreadsheets & Databases

Wire Jira to Gmail in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for freeRequest a demo