Quick Start Examples
#
These examples are perfect for your first playbooks. They demonstrate core concepts while solving real problems you can implement immediately.
Daily Customer Call Summary
#
The Request: “I want a daily summary of my customer calls that I can share with my team on Slack.”
Generated Playbook:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
| # Daily Customer Call Summary
Share key insights from customer calls with the team every morning.
## Steps
- Search Google Drive for recent customer call recordings/transcripts
- On Monday, don't forget to look back at Friday's calls
- Extract the most valuable insights, including:
- Customer pain points or feature requests
- Buying signals or objections
- Technical questions that need engineering input
- Competitive mentions
- Draft a Slack message using this format:
📞 Customer calls - [date]
**Key themes:**
• [2-3 bullet points of patterns across calls]
**Customers:**
• [Person (Role) – Company, plus additional context if required]
**Notable quotes:**
• "[customer quote]" - [context]
**Action items:**
• [specific follow-ups needed with owner and date]
- Review the message to make sure it is concise, accurate, and clear
- If no calls found: skip the update message (no need to notify about nothing)
- Post to #customer-insights channel
## Trigger
- Run weekdays at 9am
|
What this playbook does:
- Automatically finds and analyzes customer calls
- Extracts key insights and patterns
- Formats consistent, scannable summaries
- Handles edge cases like weekends and empty days
Key learning: This example shows how to create structured output templates and handle edge cases gracefully.
Daily News Summary
#
The Request: “Daily news summary”
Generated Playbook:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
| # Daily News Summary
Curate and deliver relevant news to stay informed without the noise.
## Steps
- Search for news about education technology:
- Ideally use multiple search platforms and keywords (e.g. Google, Perplexity)
- Think through the stories you find to identify the most relevant and important news
- Scrape the full contents of all the relevant stories
- Pick alternatives if any sites aren't accessible
- Identify the most significant stories based on:
- Potential business impact (for our customers and us)
- Technical breakthroughs
- Create a scannable summary:
📰 Daily news briefing - [date]
[Big picture with 1-2 sentence synthesis of the day's themes, highlighting key words/phrases in bold]
**[Concise key takeaway 1]**
• [Brief supporting detail 1/x] [Read more →](link)
[repeat for any major takeaways/supporting details]
[Optional: 2-4 one-liners + links for smaller updates]
- Send to me via Slack DM
## Trigger
- Run daily at 8am
|
What this playbook does:
- Scans multiple news sources for relevant content
- Synthesizes themes and identifies key takeaways
- Creates consistent, scannable format
- Delivers personalized briefings without information overload
Key learning: This example demonstrates information gathering, content synthesis, and personal delivery preferences.
Getting Started Tips
#
Start with These Patterns
#
- Daily summaries of information you regularly check
- Status updates that you manually compile
- Information gathering from sources you monitor
Common First Playbooks
#
- Customer call insights
- Industry news digests
- Support ticket summaries
- Team activity reports
- Social media monitoring
What Makes These Examples Work
#
- Clear input sources: Google Drive, news sites, specific data locations
- Structured outputs: Templates with emoji, headings, and bullet points
- Edge case handling: What to do when no data is found
- Appropriate timing: When your team actually needs the information
Ready for more complex examples? Check out Communication Examples or Advanced Examples.