HumationHuman + Automation
Back to Catalog

Generate daily Jira summaries & weekly reports with Azure OpenAI and Gmail

Rahul JoshiRahul Joshi
340 views
2/3/2026
File ManagementDocument ProcessingFilteringGoogle DriveMetadata Extraction
Official Page

Description 

Automates daily EOD summaries from Jira issues into an Excel sheet, then compiles a weekly summary using Azure OpenAI (GPT-4o-mini) and delivers it to stakeholders via email. Gain consistent reporting, clear insights, and hands-free delivery. ✨📧

What This Template Does 

  • Fetches Jira issues and extracts key fields. 🧩
  • Generates End‑of‑Day summaries and stores them in Excel daily. 📄
  • Aggregates the week’s EOD data from Excel. 📚
  • Creates a weekly summary using Azure OpenAI (GPT-4o-mini). 🤖
  • Delivers the weekly report to stakeholders via email. 📬

Key Benefits 

  • Saves time with fully automated daily and weekly reporting. ⏱️
  • Ensures consistent, structured summaries every time. 📏
  • Improves clarity for stakeholders with readable insights. 🪄
  • Produces mobile-friendly email summaries for quick consumption. 📱
  • No-code customization inside n8n. 🛠

Features 

  • Jira issue ingestion and transformation.
  • Daily EOD summary generation and Excel storage.
  • Weekly AI summarization with Azure OpenAI (GPT-4o-mini).
  • Styled HTML email output to stakeholders.
  • Scheduling for hands-free execution.

Requirements 

  • An n8n instance (cloud or self-hosted).
  • Jira access to read issues.
  • Azure OpenAI (GPT-4o-mini) for weekly AI summarization.
  • Email service (Gmail/SMTP) configured in n8n credentials.
  • Excel/Sheet storage set up to append and read daily EOD entries.

Target Audience 

  • Engineering and product teams needing routine summaries.
  • Project managers tracking daily progress.
  • Operations teams consolidating weekly reporting.
  • Stakeholders who prefer clean email digests.

Step-by-Step Setup Instructions 

  • Jira: Connect your Jira credentials and confirm issue read access.
  • Azure OpenAI: Deploy GPT-4o-mini and add Azure OpenAI credentials in n8n.
  • Gmail/SMTP: Connect your email account in n8n Credentials and authorize sending.
  • Excel/Sheet: Configure the sheet used to store daily EOD summaries.
  • Import the workflow, assign credentials to nodes, replace placeholders, then run and schedule.

Security Best Practices 

  • Use scoped API tokens for Jira with read-only permissions. 🔐
  • Store Azure OpenAI and email credentials in n8n’s encrypted credentials manager. 🧯
  • Limit email recipients to approved stakeholder lists. 🚦
  • Review logs regularly and rotate credentials on a schedule. ♻

n8n Workflow: Generate Daily Jira Summaries & Weekly Reports with Azure OpenAI and Gmail

This n8n workflow automates the generation of daily Jira issue summaries and weekly project reports using Azure OpenAI, then delivers these insights via email. It simplifies communication and keeps stakeholders informed without manual effort.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow can be configured to run at specified intervals (e.g., daily for summaries, weekly for reports).
  2. Fetches Jira Issues: It connects to Jira Software to retrieve relevant issues based on predefined criteria.
  3. Generates AI-Powered Summaries/Reports: Using an Azure OpenAI Chat Model and an AI Agent, it processes the Jira data to create concise daily summaries and comprehensive weekly reports.
  4. Structures Output: A Structured Output Parser ensures the AI-generated content is formatted correctly for easy consumption.
  5. Sends Email Notifications: The generated summaries and reports are then sent as emails via Gmail to designated recipients.
  6. Data Transformation (Code Node): A Code node is included, likely for custom data manipulation or formatting before AI processing or email sending.
  7. Google Sheets Integration: A Google Sheets node is present, suggesting the workflow might also read from or write to a Google Sheet, potentially for storing configurations, logging, or additional data.
  8. Sticky Note: A sticky note is included, likely for documentation or internal notes within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Jira Software Account: With appropriate API access and credentials configured in n8n.
  • Azure OpenAI Account: With an active deployment of a chat model and API key, configured as a credential in n8n.
  • Gmail Account: Configured as a credential in n8n for sending emails.
  • Google Sheets Account: (Optional, depending on specific use) If the Google Sheets node is used for data input/output, you'll need access and credentials.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Jira Software credential.
    • Set up your Azure OpenAI Chat Model credential, including your API Key and deployment details.
    • Set up your Gmail credential.
    • (Optional) Set up your Google Sheets credential if the node is actively used.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency (e.g., daily at a specific time for summaries, weekly for reports).
    • Jira Software: Configure the Jira node to fetch the specific issues relevant to your daily summaries and weekly reports (e.g., project, status, updated date).
    • AI Agent / Azure OpenAI Chat Model: Review and adjust the prompts within these nodes to guide the AI in generating the desired summaries and reports. The "Code" node might be used to prepare the input data for the AI.
    • Gmail: Specify the recipient email addresses, subject lines, and body content for the daily summaries and weekly reports. You will likely use expressions to inject the AI-generated content into the email body.
    • Google Sheets: If used, configure the sheet ID, range, and operation for reading or writing data.
  4. Activate the Workflow: Once configured, activate the workflow to start running on its defined schedule.

Related Templates

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226

Detect holiday conflicts & suggest meeting reschedules with Google Calendar and Slack

Who’s it for Remote and distributed teams that schedule across time zones and want to avoid meetings landing on public holidays—PMs, CS/AM teams, and ops leads who own cross-regional calendars. What it does / How it works The workflow checks next week’s Google Calendar events, compares event dates against public holidays for selected country codes, and produces a single Slack digest with any conflicts plus suggested alternative dates. Core steps: Workflow Configuration (Set) → Fetch Public Holidays (via a public holiday API such as Calendarific/Nager.Date) → Get Next Week Calendar Events (Google Calendar) → Detect Holiday Conflicts (compare dates) → Generate Reschedule Suggestions (find nearest business day that isn’t a holiday/weekend) → Format Slack Digest → Post Slack Digest. How to set up Open Workflow Configuration (Set) and edit: countryCodes, calendarId, slackChannel, nextWeekStart, nextWeekEnd. Connect your own Google Calendar and Slack credentials in n8n (no hardcoded keys). (Optional) Adjust the Trigger to run daily or only on Mondays. Requirements n8n (Cloud or self-hosted) Google Calendar read access to the target calendar Slack app with permission to post to the chosen channel A public-holiday API (no secrets needed for Nager.Date; Calendarific requires an API key) How to customize the workflow Time window: Change nextWeekStart/End to scan a different period. Holiday sources: Add or swap APIs; merge multiple regions. Suggestion logic: Tweak the look-ahead window or rules (e.g., skip Fridays). Output: Post per-calendar messages, DM owners, or create tentative reschedule events automatically.

Takuya OjimaBy Takuya Ojima
70

Generate event speaker recommendations with Claude AI and Google Sheets

Simplify event planning with this automated n8n workflow. Triggered by incoming requests, it fetches speaker and audience data from Google Sheets, analyzes profiles and preferences, and generates optimized session recommendations. The workflow delivers formatted voice responses and updates tracking data, ensuring organizers receive real-time, tailored suggestions. 🎙️📊 Key Features Real-time analysis of speaker and audience data for personalized recommendations. Generates optimized session lineups based on profiles and preferences. Delivers responses via voice agent for a seamless experience. Logs maintain a detailed recommendation history in Google Sheets. Workflow Process The Webhook Trigger node initiates the workflow upon receiving voice agent or external system requests. Parse Voice Request processes incoming voice data into actionable parameters. Fetch Database retrieves speaker ratings, past sessions, and audience ratings from Google Sheets. Calculate & Analyze combines voice request data with speaker profiles and audience insights for comprehensive matching. AI Optimization Engine analyzes speaker-audience fit and recommends optimal session lineups. Format Recommendations structures the recommendations for voice agent response. Voice Agent Response returns formatted recommendations to the user with natural language summary and structured data. Update Tracking Sheet saves recommendation history and analytics to Google Sheets. If errors occur, the Check for Errors node branches to: Format Error Response prepares an error message. Send Error Response delivers the error notification. Setup Instructions Import the workflow into n8n and configure Google Sheets OAuth2 for data access. Set up the Webhook Trigger with your voice agent or external system's API credentials. Configure the AI Optimization Engine node with a suitable language model (e.g., Anthropic Chat Model). Test the workflow by sending sample voice requests and verifying recommendations. Adjust analysis parameters as needed for specific event requirements. Prerequisites Google Sheets OAuth2 credentials Voice agent API or integration service AI/LLM service for optimization (e.g., Anthropic) Structured speaker and audience data in a Google Sheet Google Sheet Structure: Create a sheet with columns: Speaker Name Rating Past Sessions Audience Rating Preferences Updated At Modification Options Customize the Calculate & Analyze node to include additional matching criteria (e.g., topic expertise). Adjust the AI Optimization Engine to prioritize specific session formats or durations. Modify voice response templates in the Voice Agent Response node with branded phrasing. Integrate with event management tools (e.g., Eventbrite) for live data feeds. Set custom error handling rules in the Check for Errors node. Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
116