Skip to content
Per-pair page

Google Calendar + Jira: sprint events on the calendar.

Add Jira sprint events (kickoff, demo, retro) to Google Calendar, or block calendar time for Jira-tracked work. Useful for distributed engineering teams.

Trigger app
Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →
Action app
Google Calendar as the action

Workflows do something in Google Calendar, instantly.

Both directions

Pick the way that fits your stack.

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

JiraGoogle Calendar

When something happens in Jira, do it in Google Calendar.

6 Jira triggers wired to 7 Google Calendar actions. Most-used pairing: Comment CreatedCreate Event.

Google CalendarJira

Or fire it the other way around.

5 Google Calendar triggers wired to 17 Jira actions downstream.

See Google CalendarJira
Popular pairings

Common Jira → Google Calendar workflows.

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

Showing 9 of 42 combinations
When comment created in Jira, create event in Google Calendar.

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 event in Google Calendar.

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, get event in Google Calendar.

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, list calendars in Google Calendar.

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, create event in Google Calendar.

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 event in Google Calendar.

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, get event in Google Calendar.

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, list calendars in Google Calendar.

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, create event in Google Calendar.

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 Google Calendar in five steps.

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

  1. 1
    Connect
    Authorize Jira and Google Calendar

    Open Tiny Command, authorize Jira and Google Calendar 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 Google Calendar action

    Drop the Google Calendar → Create Event action below it. Map fields from the Jira payload into the Google Calendar inputs.

    google-calendar.create-event
  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 + Google Calendar.

How do I add Jira sprint events to Google Calendar?
Jira Sprint Started → Google Calendar Create Event for sprint kickoff. Schedule the demo and retro events on dates derived from sprint length. Whole team sees the cadence on shared calendar.
Can I block calendar focus time for a Jira issue?
Yes. Jira Issue Assigned with custom "Time Estimate" → Calendar Create Event sized to the estimate, marked as busy, on the assignee's calendar. Forces real planning over wishful estimates.
How do I create Jira issues from Calendar events?
Calendar Event Created with "[Jira]" in the title → Jira Create Issue with title and description from event. Useful for capturing meeting-decided work without manual entry.
Can I update Calendar events when Jira issues change?
Yes. Jira Issue Updated → look up linked Calendar event ID stored in issue custom field → Update Event with new title or details. Keep calendar in sync with engineering state.
How do I avoid calendar overload from per-Jira-issue events?
Only create calendar events for major milestones (sprint kickoffs, demos, retros, releases). Per-issue calendar events bury significant events in noise.
Can I post Jira sprint progress as a calendar all-day event?
Yes. Daily scheduled: compute Jira sprint % complete → Calendar Update Event (today's all-day "Sprint Progress") with the percentage in the title. Visual cue for the team daily.
Related

Other apps that pair well with Jira.


Wire Jira to Google Calendar in 2 minutes.

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