Summarise Gmail, Calendar and Slack into a daily briefing with Claude

Get Job Alerts
One email when a teaching platform opens hiring or a new AI training project drops. No weekly filler.

Executives drown in fragmented communication across email, calendar, and Slack every morning. This AI automation pulls all three channels together, scores priorities, and delivers a single actionable briefing before the first meeting starts.

What This Automation Does

Scans unread Gmail across priority labels and categorises each message by urgency so nothing important gets buried
Reviews the past three days of calendar meetings and flags any that still need a follow-up email or action item
Fetches Fireflies meeting transcripts and cross-references them against sent emails and Slack threads to confirm whether a follow-up already exists
Compiles everything into one structured daily briefing delivered automatically on weekday mornings, with a manual trigger available for on-demand runs

Tools Used

n8n
Claude
Gmail
Google Calendar
Slack
Google Sheets

Where to Get Hired for This Skill

On Contra, top freelancers across this stack have earned 337 combined verified reviews from real client projects.

Source: Contra freelancer search · refreshed 26 May 2026

Start Earning as a Freelancer on Contra

Contra is a commission-free professional network for independents. Browse live AI automation work and keep what you earn.

Join Contra Free →

How To Build It

Configure the weekday schedule trigger

Set the automation to fire at 8:00 AM on weekday mornings, and wire in a secondary manual trigger so the briefing can be regenerated on demand without waiting for the next scheduled run.

Pull and label unread Gmail by urgency

Connect Gmail to retrieve unread messages from both the To Respond and FYI labels, then pass each message through Claude to assess relationship context, identify partnership signals, and assign a High, Medium, or Low urgency rating.

Audit calendar meetings for missing follow-ups

Fetch the last three days of Google Calendar events and check each meeting against sent emails and Slack messages to determine whether a follow-up was already dispatched, flagging any meeting that still requires action.

Retrieve and parse Fireflies transcripts

For each unresolved calendar meeting, call the Fireflies API to pull the session transcript, then use Claude to extract outstanding action items and unresolved discussion points that need a response.

Compile and deliver the structured briefing

Merge the prioritised email list, calendar follow-up flags, and transcript action items into a single formatted briefing, log the output to Google Sheets for record-keeping, and post the final summary to a designated Slack channel before the workday begins.

Pitfalls

Gmail OAuth tokens expire silently after prolonged inactivity, causing the email scan to return empty results with no visible error. Build in a credential health check or alert so the client knows immediately when re-authentication is needed.
Fireflies rate limits can throttle transcript retrieval when several meetings fall on the same day. Add a delay loop between API calls and log any failed fetches to Google Sheets so no transcript is silently skipped.
Claude's summarisation style can drift over time as the memory buffer accumulates irrelevant context from older sessions. Set a deliberate window size on the memory buffer and test with a full week of synthetic email data before handing off to the client.

FAQ

Can I build this without coding?

Yes. Every integration in this workflow connects through pre-built credential blocks and visual logic, so no custom code is required. The most technical step is configuring the Fireflies API call, which involves pasting an endpoint URL and an authentication header.

How long does it take to build?

A focused build typically takes four to six hours for someone familiar with connecting APIs in n8n. Allow an additional two to three hours for testing against a live Gmail and Calendar account before delivery.

What can I charge for this?

Pricing is your decision based on your market and positioning. The brief frames this as a Communication Command Center setup service, which justifies a premium over simple single-tool automations given the number of integrations and the ongoing value to the client.

Which tools are required versus optional?

Gmail, Google Calendar, Claude, and Slack are core to the briefing logic and cannot be removed without rebuilding significant parts of the workflow. Google Sheets is optional but strongly recommended for audit logging. Fireflies is optional if the client does not record meetings, in which case the transcript step can be skipped or replaced with manual notes input.

This is original DigiNo analysis. The underlying automation pattern is a community workflow template – view the original on n8n.