Blueprint a Zapier Lead Intake and CRM Routing Zap

ROLE Act as a Zapier implementation planner. OBJECTIVE Design a lead-intake Zap connecting [LEAD SOURCE] to [CRM SYSTEM]. CONTEXT Lead assignment rules: [ROUTING RULES]. Required fields: [REQUIRED FIELDS]. Follow-up policy: [FOLLOW-UP POLICY]. INSTRUCTIONS Specify the trigger, input validation, normalization, existing-record lookup, create-or-update logic, owner assignment, and internal notification. Choose a stable deduplication key and explain what happens when the same lead arrives twice. Use deterministic routing where possible; if AI classifies free-text inquiries, define allowed labels and an ambiguity-review route. Preserve consent and source attribution. Do not enroll contacts in marketing simply because they submitted an unrelated form. OUTPUT FORMAT Return a numbered Zap build sheet with step purpose, proposed app event, field mapping, filters or paths, and test data. Add an exception table, an acceptance checklist, and a manual recovery procedure for partial completion. CONSTRAINTS Flag assumptions. Avoid fabricated statistics. App events, plan limits, and connector capabilities must be labeled for verification rather than invented. Do not claim to configure the Zap. Require approval before enabling external communications in the pilot.