Back to Catalog

Automated sprint reports from Jira to stakeholders via Gmail

Yassin ZeharYassin Zehar
524 views
2/3/2026
Official Page

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

image.png

  • 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.

image.png

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

Automated Sprint Reports from Jira to Stakeholders via Gmail

This n8n workflow automates the process of generating and distributing sprint reports from Jira to relevant stakeholders via email. It's designed to streamline communication, ensuring that everyone is kept up-to-date on project progress without manual intervention.

What it does

This workflow, as defined by its JSON, currently includes the following components:

  1. Schedule Trigger: Initiates the workflow at predefined intervals. This is the starting point for the automated process.
  2. Jira Software: Connects to Jira, likely to fetch sprint data, issue statuses, or other relevant project information.
  3. Edit Fields (Set): A utility node for manipulating or transforming data. This could be used to format Jira data into a digestible report structure.
  4. Code: A custom code execution node, likely used for advanced data processing, report generation logic, or dynamic content creation based on the Jira data.
  5. Gmail: Sends emails, which would be used to distribute the generated sprint reports to stakeholders.
  6. Sticky Note: A documentation node for adding notes or explanations within the workflow itself.

While the connections between these nodes are not explicitly defined in the provided JSON, the presence of these nodes strongly suggests a flow where:

  • The workflow is triggered on a schedule.
  • It retrieves data from Jira.
  • The Jira data is processed and formatted (potentially using the "Edit Fields" and "Code" nodes).
  • A report is generated and then sent out via Gmail.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Jira Account: Access to a Jira instance with appropriate permissions to read project and sprint data. You will need to configure a Jira credential in n8n.
  • Gmail Account: A Gmail account or Google Workspace account configured as a credential in n8n, with permissions to send emails.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Locate the "Jira Software" node and configure your Jira credentials. This typically involves providing your Jira URL, username, and an API token.
    • Locate the "Gmail" node and configure your Google OAuth2 credentials. This will allow n8n to send emails on your behalf.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency (e.g., weekly, bi-weekly) for sending sprint reports.
    • Jira Software: Configure this node to fetch the specific sprint data, issues, or project information you need for your reports. You'll likely specify the project, board, and sprint ID.
    • Edit Fields (Set): Customize this node to transform the raw Jira data into a structured format suitable for your report.
    • Code: If present, review and modify the JavaScript code to implement your specific report generation logic, data aggregation, or dynamic content.
    • Gmail: Configure the recipient email addresses, subject line, and email body. You will likely use expressions to dynamically insert data from previous nodes into the email content.
  4. Activate the Workflow: Once configured, activate the workflow to enable it to run automatically on its defined schedule.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247