Automated sprint reports from Jira to stakeholders via Gmail

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Description Automated workflow that generates a Sprint Report from Jira and delivers it by Gmail. The flow fetches sprint issues from Jira, validates and normalizes the data, calculates metrics (ti...

Best for

Project Management automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.gmail, n8n-nodes-base.jira, n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.code

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Yassin Zehar.

Original n8n.io source

1.1 Workflow description

Title: Automated sprint reports from Jira to stakeholders via Gmail
Workflow name: Automated sprint reports from Jira to stakeholders via Gmail

Description

Automated workflow that generates a Sprint Report from Jira and delivers it by Gmail.

The flow fetches sprint issues from Jira, validates and normalizes the data, calculates metrics (tickets, story points, blockers, completion rate), generates an HTML report, and sends it by email.

Context

This template helps teams keep stakeholders updated automatically of the current sprint. Instead of manually compiling Jira data, the report is generated and sent on schedule (e.g., every Friday at 17:00).

It’s production-friendly, reusable, and works across Jira projects.

Target Users

Scrum Masters and Agile Coaches who need sprint reports for retrospectives.
Product Owners who want a weekly overview of sprint progress.
Project Managers tracking Jira delivery KPIs.
Engineering teams wanting automated status reporting without extra overhead.

Technical Requirements

Jira Cloud project + API email + API token + permission to read issues.
Gmail credential for notifications.

Workflow Steps

Trigger – Schedule (e.g., Friday at 17:00).
Edit Fields – Configure Jira base URL, project key, email recipients.
Get Many Issues – Fetch sprint issues with JQL (project = <KEY> AND sprint in openSprints()).
Validation & Normalization – Clean/validate fields (status, assignee, priority, story points, sprint info).
Metrics Calculation – Aggregate KPIs (done, in progress, blockers, story points, completion %).
HTML Report Generation – Build a styled email-friendly HTML summary + detailed table.
Send Gmail – Deliver report to stakeholders.

Key Features

Automated Sprint Reports: No manual copy-paste.
Metrics overview: Tickets done vs total, blockers, story points.
Detailed table: Issue key, summary, status, assignee, priority, SP.
Email delivery: HTML report with Jira links sent to stakeholders.
Fully customizable: Adjust fields, KPIs, and recipients easily.

Expected Output

📊 HTML Sprint Report with KPIs and issue table. ✅ Email delivered to stakeholders via Gmail. 🔗 Jira links embedded for easy navigation.

How it works

⏰ Trigger – Runs on schedule (e.g., every Friday at 17:00). 🧾 Fetch Issues – JQL filters sprint tickets. 📊 Metrics – Done vs total, SP progress, blockers. 💻 Generate HTML – Clean, styled table and summary. ✉️ Notify – Send Gmail with full sprint report to stakeholders.

Tutorial video:

Watch the Youtube Tutorial video

About me :

I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Email notification

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 2 - Get many issues

Type / Role: n8n-nodes-base.jira - jira
Config choices: Version 1

Block 3 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 6 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 7 - Weekly trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 8 - Jira & email configuration

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 9 - Validation & error handling

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 10 - Metrics calculation

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 11 - HTML report generation

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

3. Summary Table

Workflow	Automated sprint reports from Jira to stakeholders via Gmail
Complexity	intermediate
Nodes	11
Categories	Project Management
Author	Yassin Zehar
Published	25 Sept 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/8932/8932.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Project Management workflows

Frequently asked questions

What does Automated sprint reports from Jira to stakeholders via Gmail do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management use case.

Yassin Zehar

19 workflows

Nodes

n8n-nodes-base.gmail n8n-nodes-base.jira n8n-nodes-base.stickynote n8n-nodes-base.scheduletrigger n8n-nodes-base.set n8n-nodes-base.code

Complexity

intermediate

Published 25 Sept 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/8932/8932.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Tag stale ClickUp tasks and escalate overdue items with assignee comments

## Quick overview This workflow runs daily on a schedule and checks ClickUp tasks in one or more lists for inactivity based on the task’s date_updated field, automatically applying “stale” tags and escalating long-idle tasks by tagging them and posting an assignee comment. ## How it works 1. Runs every day at the configured hour using the schedule trigger. 2. Loads monitoring settings (statuses, tags, stale thresholds, and tag names) and fetches matching tasks from the selected ClickUp list(s), then merges and deduplicates them. 3. Skips tasks that already have the second-level stale tag (for example, stale:14). 4. For tasks without the first-level stale tag, checks the last updated timestamp and adds either the first-level stale tag (for example, stale:7) or the second-level stale tag if they already exceed the higher threshold. 5. For tasks that already have the first-level stale tag, checks whether enough time has passed since that tag was applied and, if so, removes the first-level tag and adds the second-level stale tag. 6. When a task is escalated to the second-level stale tag, posts a warning comment on the ClickUp task and assigns the comment to the task assignee (or the creator if no assignee exists). ## Setup 1. Add a ClickUp API credential (OAuth or API token) and select it on all ClickUp nodes. 2. In the ClickUp task search node(s), choose the list(s) you want to monitor and enable/configure the second list node if you want to pull tasks from multiple lists. 3. Update the monitoring settings (monitoredStatuses, monitoredTags, daysUntilFirstStaleTag, daysUntilSecondStaleTag, and the stale tag names) to match your ClickUp workspace conventions. 4. Adjust the schedule trigger time and, if needed, set the workflow timezone in n8n settings so the run time matches your local time. ## Requirements - A ClickUp account with API access - ClickUp credential configured in n8n - At least one ClickUp list to monitor ## Customization - Change thresholds — Edit `daysUntilFirstStaleTag` and `daysUntilSecondStaleTag` in `SetContext` to any number of days - Change tag names — Update `firstStaleTagName` / `secondStaleTagName` to match your ClickUp tag naming convention - Monitor different statuses — Edit `monitoredStatuses` and `monitoredTags` in `SetContext` (e.g. add `review`, `blocked`) - Add more lists — Duplicate `GetTaskFromList1`, update the List ID, enable the node, and connect its output to a new input port on `AppendListTasks` - Change schedule — Open `TriggerRegularly` and switch from daily to weekdays-only or any custom cron interval - Disable subtasks — Open each `GetTaskFromList` node and set `subtasks` to `false` in the Filters section

View

Summarize daily Slack standups with OpenAI, Notion, and Google Sheets

## Quick overview This workflow runs every weekday, pulls standup messages from a Slack channel, uses OpenAI to generate a structured daily digest, saves the digest to a Notion database, posts a summary back to Slack, and appends an audit entry to Google Sheets. ## How it works 1. Runs every weekday morning on a cron schedule. 2. Fetches the day’s recent messages from a specified Slack standup channel and filters out bot, subtype, and join/leave system messages. 3. Checks whether any standup messages remain and posts a Slack notice if none are found. 4. Formats the remaining Slack updates into a single structured prompt with date, team name, and message count. 5. Sends the formatted standup text to OpenAI (gpt-4.1-mini) to generate a JSON digest with summary, highlights, blockers, per-user updates, and mood. 6. Parses and enriches the AI output with metadata, creates a new page in a Notion database, posts the digest to a Slack summary channel, and appends a run record to a Google Sheets “Audit Log” sheet. ## Setup 1. Add a Slack OAuth2 credential and set the standup channel ID (history source) and the summary channel ID (digest destination). 2. Add an OpenAI credential and confirm the model selection (gpt-4.1-mini) is available in your account. 3. Add a Notion credential, create/select a target database, and replace `YOUR_NOTION_DATABASE_ID` (and ensure the database has the referenced properties: Date, Team, Message Count, Mood). 4. Add a Google Sheets Service Account credential, share the target spreadsheet with the service account email, and replace `YOUR_SHEET_ID` and the sheet name (“Audit Log”) if different. 5. Adjust the schedule cron expression (`0 9 * * 1-5`) to match your team’s standup timing and timezone expectations.

View

Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

## Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all-day events in Google Calendar, then posts a creation or update notice to a Telegram group. ## How it works 1. Polls Google Sheets every hour for any updates in the “Check Inventory” sheet. 2. Checks whether the updated row already contains a Google Calendar Event ID. 3. If the Event ID is empty, searches Google Calendar for an existing event whose text matches the check number and backfills the found Event ID to Google Sheets. 4. If no matching calendar event exists, creates an all-day Google Calendar event using the check date and details from the Google Sheets row, then writes the new Event ID back to the sheet. 5. If an Event ID exists, fetches the corresponding Google Calendar event and compares its date, summary, and description to the latest Google Sheets values. 6. When differences are detected, updates the Google Calendar event to match the sheet and sends a Telegram message summarizing the created or updated events. ## Setup 1. Connect credentials for Google Sheets (including Google Sheets Trigger), Google Calendar OAuth2, and a Telegram Bot API account. 2. Replace `YOUR_CHECK_INVENTORY_SHEET_ID` in all Google Sheets nodes and ensure the “Check Inventory” sheet contains the required columns (including “Check Number” and “Event ID”). 3. Set the target Google Calendar ID (for example `[email protected]` or a shared calendar ID) in the Google Calendar nodes. 4. Replace `YOUR_TELEGRAM_GROUP_CHAT_ID` in the Telegram nodes and edit the message text to use the correct @mentions for your team.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Automated sprint reports from Jira to stakeholders via Gmail

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Description

Context

Target Users

Technical Requirements

Workflow Steps

Key Features

Expected Output

How it works

Tutorial video:

About me :

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Email notification

Block 2 - Get many issues

Block 3 - Sticky Note1

Block 4 - Sticky Note

Block 5 - Sticky Note2

Block 6 - Sticky Note3

Block 7 - Weekly trigger

Block 8 - Jira & email configuration

Block 9 - Validation & error handling

Block 10 - Metrics calculation

Block 11 - HTML report generation

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions