Chaining tools
Build multi-step workflows that span email, calendar, Drive, and web
The real power: crossing tool boundaries
Each connected tool is useful individually. But the real power emerges when Claude can move across tools in a single workflow — reading from Drive, checking calendar, searching email, creating documents, drafting messages — without you having to coordinate between them.
Example: new lead intake workflow
"A new lead just emailed us. Here's the email: [paste email]
Handle the intake:
1. Search Drive for any past interactions with this contact or company
2. Check my calendar for availability next week for a 45-minute discovery call
3. Search my email for any prior threads with them
4. Create a new prospect folder in Drive at /BConverse/Prospects/[name]/
5. Create a prospect brief with what we know about them
6. Draft a reply email offering 3 call times from step 2
Do steps 1-5 fully, then show me the draft from step 6 before we proceed."
Example: weekly business review
"Run my weekly business review:
1. Check calendar: what's on my schedule this week?
2. Check email: any urgent items from clients in the last 48 hours?
3. Check Drive: find each active project folder, read status notes
4. Synthesize into a weekly brief:
- This week's priorities (from calendar + email)
- Project status for each active client
- Any red flags or blocked items
Save the brief to Drive at /BConverse/Internal/Weekly/[date]-review.gdoc"
Example: project close workflow
"The [project name] project is wrapping up. Run the close workflow:
1. Find the project folder in Drive — read all deliverables
2. Check email for the last 4 weeks of client correspondence
3. Create a project close summary document
4. Draft a close email to the client
5. Archive the project folder
Show me the close email draft before anything is sent or archived."
Design principle: The best cross-tool workflows have a clear trigger, well-defined steps with explicit tool assignments, and a human checkpoint before any irreversible action.
Quizzes