Use Case and Problem
Engineering and analytics teams struggle to maintain a single source of truth for team context. Important information lives in scattered documents - project trackers in Excel, status reports in PDF, onboarding guides in Word, and process docs in Markdown. Team members constantly ask the same questions: “What’s the deploy success rate this week?”,“Who owns the Data Ingestion project?”,“What are our communication norms?”
Manually pulling this information together every week for stakeholders wastes hours and produces stale results by the time the email is sent.
What if you could set up a Quick Flow that automatically reads all your team documents — regardless of format — synthesizes a structured intelligence brief, and delivers it to your team’s inbox via Outlook? No manual copy-paste, always fresh, always consistent.
This article shows you how to build exactly that using three Quick Suite capabilities:
- Spaces - for structured document storage and querying,
- Flows - for automated data synthesis and delivery, and
- Integrations - for connecting to Outlook email.
How to Solve the Problem
This walkthrough demonstrates building a Flow that reads across multiple file formats (Excel, PDF, Word, Markdown) stored in a Space, produces a Team Intelligence Brief, and emails it to stakeholders via Outlook.
Prerequisites
Before starting, ensure you have the following:
- A Quick Suite account with access to Spaces, Flows, and Integrations
- Outlook integration connected (for email delivery)
- Author/Admin permissions on your Space
- A set of team documents uploaded to your Space (we’ll use the example set below)
Example Documents in Our Space
| File | Format | Contents |
|---|---|---|
| team-metrics-tracker.xlsx | Excel | 3 sheets: Weekly Metrics (with formulas & chart), Deployments log, Team Capacity |
| project-status-report.pdf | 3-page status report with project table, risk section, and team health metrics | |
| onboarding-guide.docx | Word | Team onboarding guide with roster table, first-week checklist, key resources |
| team-roster.md | Markdown | Team members, roles, norms |
| active-projects.md | Markdown | 4 projects with status & milestones |
| metrics-week-20.md | Markdown | Weekly metrics snapshot |
| metrics-week-21.md | Markdown | Weekly metrics snapshot |
| glossary-and-definitions.md | Markdown | KPI definitions & acronyms |
| faq.md | Markdown | Process & technical FAQ |
Step-by-Step Solution
Step 1: Create and Populate Your Team Space
Set up a dedicated Space that serves as your team’s single source of truth.
1. Navigate to Quick Suite → Spaces and click Create Space.
2. Name it `Data Team Knowledge Base`.
3. Upload your documents. Quick Suite supports multiple file formats:
4. Verify your uploads by listing the Space contents. You should see all 9 files indexed and queryable.
Tip: Use a consistent naming convention. Prefix time-based files with the period (e.g., `metrics-week-20.md`) so Flows can easily identify the latest data.
Step 2: Connect Outlook Integration
Enable Outlook so your Flow can send the generated brief via email.
1. Go to Settings → Capabilities → Connections.
2. Click Outlook and authenticate with your work account.
3. Verify the connection by sending a test email to yourself.
Once connected, your Flow can compose and send emails — including formatted HTML bodies with tables, status indicators, and structured data.
Step 3: Create the Team Intelligence Brief Flow
This is the core automation. Create a Flow that reads all documents in your Space, synthesizes insights, and delivers them.
3a. Create the Flow
1. Navigate to Quick Suite → Flows and click Create Flow.
2. Name it: `Team Intelligence Brief (with Email Delivery)`
3. Add the following description:
Name: Team Intelligence Brief (with Email Delivery)
Description: Generate a comprehensive team intelligence brief by reading all documents in the "Data Team Knowledge Base" space, synthesizing a summary with context and updates, and emailing it to the team via Outlook.
This flow reads across all file types in the space:
- team-metrics-tracker.xlsx (Weekly Metrics, Deployments, Team Capacity)
- project-status-report.pdf (Project status, risks, health metrics)
- onboarding-guide.docx (Team roster, resources, norms)
- active-projects.md (Project statuses & milestones)
- team-roster.md (Team members & roles)
- metrics-week-20.md and metrics-week-21.md (Weekly snapshots)
- glossary-and-definitions.md (KPI definitions)
- faq.md (Process & technical FAQ)
It produces a single structured brief with the following sections:
1. TEAM SNAPSHOT
- Team size, roles, and current on-call from team-roster.md and onboarding-guide.docx
- Who is over-scheduled this week from team-metrics-tracker.xlsx (Team Capacity sheet)
2. PROJECT UPDATES
- Current status of all active projects from active-projects.md
- Risks and blockers from project-status-report.pdf
- Milestone progress (what moved since last update)
3. METRICS SUMMARY
- Latest weekly metrics from team-metrics-tracker.xlsx (Weekly Metrics sheet)
- Week-over-week trend comparison using metrics-week-20.md and metrics-week-21.md
- Deploy success rate and deployment log highlights from team-metrics-tracker.xlsx (Deployments sheet)
- Flag any metric that misses its target (targets defined in glossary-and-definitions.md)
4. ACTION ITEMS & WATCH LIST
- Open action items count and trend
- Any KPI below target threshold
- Team members with meeting load >4 hrs/day
- Stale blockers (risks from PDF that haven't been resolved)
5. QUICK CONTEXT (for new joiners or stakeholders)
- One-line summary of each active project
- Link to FAQ for common process questions
- Key communication norms from onboarding-guide.docx
OUTPUT & DELIVERY:
- Format the brief as a well-structured HTML email with clear headings, tables for metrics, and color-coded status indicators (🟢 on track, 🟡 at risk, 🔴 blocked)
- Send via Outlook to the team distribution list
- Subject line: "[Team Brief] Weekly Intelligence Summary — {date}"
- Include a one-line TL;DR at the top of the email body
- Attach the full brief as a PDF if the content exceeds 500 words
Trigger: Schedule - Every Monday at 9:00 AM IST
Recipients: Team distribution list (or specify individual emails)
Step 4: Test and Validate
Before setting the Flow to run on schedule:
1. Run the Flow manually once to verify output quality.
2. Check the email - confirm formatting renders correctly in Outlook.
3. Validate data accuracy - spot-check 2-3 numbers against the source documents.
4. Adjust the schedule if needed (daily for fast-moving teams, weekly for steady-state).
Step 5: Add an Alert Agent (Bonus)
Layer an Agent on top of your Flow for proactive alerting:
1. Go to Quick Suite → Agents and create a new Agent.
2. Name it `Metrics Alert Monitor`.
3. Configure:
- Trigger: Daily at 9:30 AM (after the Flow runs)
- Logic: Read the Space for latest metrics. If any metric crosses a threshold (e.g., deploy success rate < 90%, action items > 10, any teammate with >5 hrs meetings/day for 3+ days), send an alert.
- Action: Send an Outlook email to the team lead with the specific alert.
Example alert:
Metrics Alert: Deploy success rate dropped to 72% (threshold: 90%). 3 failed deploys on `auth-service` this week. Team member Priya Sharma has been over-scheduled (>5 hrs meetings/day) for 4 consecutive days.
Architecture Overview
Conclusion
By combining Spaces (multi-format document storage), Flows (automated reading, synthesis, and delivery), and Integrations (Outlook email), you can build a team intelligence system that stays current without manual effort. Your team gets a consistent, well-formatted brief in their inbox every Monday — pulling from Excel metrics, PDF reports, Word guides, and Markdown docs alike.
Start by uploading your existing team documents to a Space, create a Flow that reads and synthesizes them, and connect Outlook for delivery. The modular architecture means you can add new documents or change the delivery schedule without rebuilding anything.
Author & Company Bio
Shatakshi Pandey is a Delivery Consultant in Data & Analytics at AWS Professional Services. She specializes in designing and delivering AWS cloud-based solutions and accelerating customers migration journey from existing workloads to the cloud.
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.