Notion CRM Form Routing & Automated Client Intake

The Problem vs. The Outcome

Before

Four forms dumping into one shared Gmail inbox
No tagging, routing, or categorization
Leads slipping through the cracks daily
Hours spent each week manually copying contact data
No consistent follow-up process

After

Every submission instantly routed to a tagged Notion CRM record
Conditional auto-responses firing per form type via Notion Sender
Real-time Slack alerts for the internal team on every new contact
Zero manual data entry across the entire intake pipeline
Complete follow-up consistency from day one

How It Was Built

Step 1

Identify & Map

Audited all four forms, their fields, and what each submission should trigger downstream.

Step 2

Build CRM Architecture

Designed the Notion CRM structure: contact fields, tagging taxonomy, city labels, intake status, and source tracking.

Step 3

Zapier Workflow per Form

Built four independent Zaps — one per form — each creating a correctly tagged Notion contact record on submission.

Step 4

Conditional Auto-Response

Layered logic in Zapier to fire the right Notion Sender email based on which form triggered the workflow.

Step 5

Slack Notifications

Added a final Slack notification step to each Zap so the team is alerted in real time when a new contact enters the CRM.

Step 6

Test & Validate

Ran full end-to-end tests for every form, verified CRM entries, email delivery, and Slack alerts before going live.

Project Timeline

Day 1–2: Discovery, form audit, and CRM field mapping

Identified all form sources and defined the Notion schema.

Day 3–4: Notion CRM database setup and taxonomy design

Built the database structure and tagging system.

Day 5–7: Zapier workflow builds for all four forms

One Zap per form, each creating tagged CRM records.

Day 8–9: Auto-response email logic and Notion Sender configuration

Conditional emails per form type.

Day 10: Slack notification setup

Real-time alerts for the team.

Day 11–14: End-to-end testing, edge case handling, and client handoff

Full validation and documentation.

Full Breakdown

The Problem

The organization was running four separate website forms — a general contact form, a service inquiry form, a program registration form, and a newsletter signup — but every submission funneled into a single shared Gmail inbox. There was no tagging, no routing, and no follow-up consistency. Leads were slipping through the cracks regularly, and the team was spending hours each week manually copying contact details into spreadsheets just to maintain a basic record of who had reached out.

The Approach

Before touching any tools, I mapped the full intake logic on paper — identifying what data each form collected, how contacts should be categorized in the CRM, and what the appropriate follow-up looked like for each submission type. This upfront mapping is what separates a clean automation build from one that creates new problems six weeks later.

The Build

I built four independent Zapier workflows, one per form, each designed to create a precisely tagged contact record in their Notion CRM the moment a submission came in. Fields were mapped carefully: source, form type, city, date of entry, and intake status. I then layered in conditional logic to trigger the right auto-response email through Notion Sender based on the form type — a registration confirmation felt different from a general inquiry response, and that distinction mattered for the client's brand. A final Slack notification step on each Zap kept the internal team informed in real time.

The Result

The client went from a chaotic shared inbox to a fully automated intake pipeline. Every submission is now routed, tagged, and responded to automatically. The team gets notified instantly. And the Notion CRM stays current and accurate without anyone having to touch it.