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 Gmail and Jira See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Jira as the action

Workflows do something in Jira, instantly.

See all 17 actions →

Both directions

Pick the way that fits your stack.

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

Gmail → Jira

When something happens in Gmail, do it in Jira.

1 Gmail triggers wired to 17 Jira actions. Most-used pairing: New Email → Add Comment.

New Email

Jira → Gmail

Or fire it the other way around.

6 Jira triggers wired to 27 Gmail actions downstream.

See Jira → Gmail →

How it works

Connect Gmail and Jira in five steps.

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

1
Connect
Authorize Gmail and Jira
Open Tiny Command, authorize Gmail and Jira once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
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
Action
Add the Jira action
Drop the Jira → Add Comment action below it. Map fields from the Gmail payload into the Jira inputs.
jira.add-comment
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 Gmail + Jira.

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.