Design an AI Workflow That Sticks · Lesson 4 of 7

Lesson 4 — Connecting AI to email, calendar, docs

45 minutes. No code. How to move AI in and out of the tools you already use.

---

The four no-code integration patterns

Pattern 1 — Copy-paste workflows. You manually move data in and out of AI. Lowest cost, highest friction. Good for daily-use workflows you do consciously.

Pattern 2 — Side panels in your existing tools. Claude's Chrome extension. ChatGPT in Edge sidebar. Microsoft Copilot in Outlook/Word. AI lives next to the work — no tab-switching.

Pattern 3 — Forwarded email or shared inbox. Set up a special email address (e.g., `triage@yourbiz.com`). Forward customer emails there. A no-code automation (Zapier, Make, or Microsoft Power Automate) feeds them to AI and posts the result to Slack or a draft in Outlook.

Pattern 4 — Calendar-triggered automations. A weekly script (no-code) gathers the week's work, sends it to AI, and emails you the summary every Friday at 4pm.

When to use which

Daily, conscious workflow (you decide when to run it): Pattern 1 or 2.
Reactive, always-on workflow (something arrives → AI handles): Pattern 3.
Periodic, scheduled workflow (every Monday, every Friday): Pattern 4.

The big rule

Never let AI write directly to a customer-facing surface. AI writes to a *draft* — a draft email, a draft document, a draft reply. A human approves the draft and clicks send.

This is the difference between "AI saves time" and "AI got us sued."

→ Lesson 5 — Approval loops and audit trails

Previous: Lesson 3 — Designing prompts that survive real use · Next: Lesson 5 — Approval loops and audit trails