Sales Workflow Automation: Gmail + Notion + Airtable
Prospect emails you → Claude reads it, creates an Airtable deal record, and drafts a Notion context page. You review and send the reply. The whole intake handled without touching a spreadsheet.
The first response to a sales inquiry sets the tone for the entire relationship. It also takes 20 minutes of context-gathering, CRM updating, and email drafting that a human shouldn't be doing manually. Claude can do all three — the key is making sure the reply goes to the prospect only after you've reviewed it.
The Sales Intake Pipeline
Permission Configuration
Gmail
Goes to a real prospect — always needs your sign-off
Airtable
Notion
The Sales Intake Prompt
"Read the most recent unread email that looks like a sales inquiry. Then: 1) Check the Airtable CRM to see if this person or company already exists. If not, create a new deal record with their name, company, email, and a brief summary of what they're asking about. Set the stage to 'New Inquiry.' 2) Search Notion for any existing pages about this company. Create a deal context page with: company summary, what they're asking for, suggested talking points, and any relevant questions to clarify. 3) Draft a reply in Gmail that's warm, professional, and asks 1-2 clarifying questions. Present all three for my review — don't send the email."
Why Each Service Gets Its Role
Airtable
Structured pipeline data. Deal stage, contact info, next action. Queryable, filterable, shareable with the team.
Notion
Qualitative context. Company research, conversation history, talking points. Free-form and searchable.
Gmail
The actual communication. Stays in your control — Claude drafts, you send.
Keeping Deal Data Out of the AI's Context Window
One of the less obvious risks in AI + CRM workflows: the AI reading your entire CRM means your entire CRM is in its context window. Claude sees deal values, client names, contract terms — and that data can appear in AI provider logs.
Stow's Zero-Retention policy strips Airtable response content before it reaches the database — so your deal data isn't stored on Stow's servers. But the data still passes through Claude's context. The practical mitigation: scope what Claude reads. Instead of "read all deals," use "check if this specific contact exists" and "create a new record." Claude sees the minimum needed for the pipeline step.
Prompts for Follow-Up Steps
Stow Security Team
April 19, 2026