Zapier Client Onboarding & Follow-up Automation

Overview

Project Overview

A client onboarding workflow for service businesses that need a reliable handoff from incoming inquiry to CRM record, follow-up reminder, and internal notification without sending uncontrolled outbound emails.

Zapier Webhooks Formatter Filter Airtable Gmail Google Calendar Telegram Bot

POST /client-onboarding-webhook

POST

/client-onboarding-webhook

{

"client_name": "Mira Keller",

"email": "mira.keller@example.com",

"service_interest": "Client Follow-up Automation"

}

200 OK

{

"crm_record": "created",

"gmail_draft": "prepared",

"calendar_event": "scheduled",

"telegram_alert": "sent"

}

⚠

Problem

New client inquiries can be missed, duplicated, or left without a clear follow-up owner when intake happens manually.

✓

Solution

A Zapier workflow captures intake data, validates the email, creates the CRM record, drafts a reply, schedules follow-up, and alerts the operator.

🛡

Production Safety

The system creates a Gmail draft instead of sending automatically, reducing the risk of incorrect client-facing communication.

Architecture

Nine steps, one clean action.

The workflow is deliberately linear and auditable. Each step has one responsibility, with the follow-up date calculated before CRM creation so the Airtable record can be written in a single clean action. Click any step to inspect it.

Click a node to inspect it

A Zapier onboarding flow: webhook intake, validated Airtable record, a Gmail draft, a Calendar follow-up and a Telegram alert.

Data Flow

Verified end to end.

The final test used a new client profile and verified all downstream outputs across Airtable, Gmail, Google Calendar, and Telegram.

⬆

Input

Mira Keller submitted a beauty studio automation request with email, phone, service interest, preferred contact method, and message.

⬇

Output

The system created a CRM record, prepared a Gmail draft, scheduled a follow-up event, and sent an internal Telegram confirmation.

The Zap was turned off after proof to avoid unnecessary duplicate CRM records, Gmail drafts, calendar events, and Telegram messages.

Proof, not mockups

Proof Screenshots

Final working evidence from the completed Zapier onboarding workflow. Click any image to enlarge.

Zapier workflow — intake and validation

Webhook trigger, email normalization, email filter, Airtable lookup, and follow-up date calculation.

Zapier workflow — actions and notifications

Airtable record creation, Gmail draft, Google Calendar follow-up event, and Telegram notification.

Airtable CRM record

The final client record was created in Client_Onboarding with normalized email, service interest, status, follow-up date, and source.

Gmail draft prepared

The automation created a reviewable client-facing draft instead of sending automatically.

Telegram internal notification

The operator receives a compact confirmation that CRM, Gmail draft, and calendar follow-up were completed.

Google Calendar follow-up event

A calendar reminder was scheduled with client details, service interest, original message, and automation source.

Skills Demonstrated

Beyond app-to-app automation.

This project demonstrates workflow orchestration and operational design beyond simple app-to-app automation.

🔗

Webhook Intake

Built a webhook-triggered entry point that can later connect to a landing page, form, or external system.

🧹

Data Hygiene

Normalized email input and used a required-email filter before creating operational records.

📁

CRM Operations

Created structured Airtable onboarding records with source tracking and follow-up metadata.

✉

Safe Client Communication

Generated Gmail drafts instead of automatic sends to preserve human review.

📅

Follow-up Discipline

Scheduled Google Calendar reminders with enough context to act without searching through records.

🔔

Internal Notifications

Sent Telegram alerts that confirm all important downstream actions.

Notes

Limitations & Production Notes

The workflow is production-style but intentionally kept safe for portfolio demonstration.

⚠

Current Limitation

The demo version proves find/create behavior, but a full production version should add a separate update path for existing clients if repeat inquiries need to refresh status or follow-up data.

🔧

Recommended Hardening

Add stronger payload validation, timezone normalization for calendar scheduling, error logging, and environment-specific webhook URLs before using it with real clients.