n8n Morning Brief Automation: Jira, Gmail, Slack + Groq

Get a complete “Morning Brief” in Slack—automatically

This n8n workflow schedules a daily roundup that pulls Jira support tickets, integration/API health metrics (via HTTP), unread Gmail messages, and Slack signals—then uses Groq-hosted LLMs to correlate everything into a single, prioritized Markdown morning brief sent to a specified Slack user.

What this workflow does

• Runs on a schedule and simultaneously retrieves data from Jira, an HTTP endpoint for integration health, Gmail (unread emails), and Slack signals.
• Checks Jira for issues; if issues are returned, it extracts issue data and processes items in batches.
• Uses Groq LLM analysis to produce structured summaries of: Jira tickets, integration health output, partner follow-up emails, and team signals.
• Merges the analyzed results into a combined input set, while also collecting any retrieval or AI-analysis errors.
• Deduplicates, correlates, and prioritizes items with a Groq LLM, then formats the output into a Markdown “Morning Brief” with sections for Email, Jira/Tasks, and API/System Metrics.
• Sends to Slack; if metrics retrieval fails, it posts a fallback API-status warning instead.

Use cases

• Daily status communication for SaaS operators who need actionable triage across Jira, API health, and partner follow-ups.
• Operations teams turning unread Gmail and Slack signals into a single prioritized digest.
• Automation engineers standardizing an n8n morning brief workflow for consistent cross-system reporting.

Technical details

• Integrations/credentials: Jira Software Cloud, Gmail (OAuth2), Slack, and a Groq API account.
• Data sources: Jira, HTTP Request (configurable URL + auth such as Bearer token), Gmail unread messages, and Slack signals.
• Nodes used (per workflow): if, set, code, jira, no op, gmail (plus supporting HTTP/Groq steps as described).

Setup checklist: connect credentials, configure the HTTP Request node URL/auth, then update the Jira query plus Gmail/Slack filters.