Workflow Automation Reliability Auditor

Audit this Zapier workflow for reliability:

Workflow: Website form submission to CRM lead creation, Slack notification, and Google Sheet logging.

Known issue: Sometimes duplicate CRM leads are created.

Current flow:

1. Website form submission triggers the Zap.
2. Zap creates a new lead in the CRM.
3. Zap sends a Slack alert to the sales channel.
4. Zap adds a row to a Google Sheet.

Please identify:

• failure points
• duplicate-data risks
• data-loss risks
• missing retry logic
• missing logging
• missing fallback paths
• business impact
• prioritized fixes
• testing checklist

=== ZAPIER WORKFLOW RELIABILITY AUDIT ===

Zap: Website form to CRM lead, Slack alert, and Google Sheet logging.

Trigger: New website form submission.

Actions:

1. Create CRM lead.
2. Send Slack notification.
3. Add row to Google Sheet.

Primary reliability issue: The workflow appears to create a CRM record without a lookup-before-create step. If the form sends duplicate submissions or Zapier retries after a temporary failure, duplicate CRM leads may be created.

Risk severity: High.

Why it matters: Duplicate CRM leads can split sales activity, confuse ownership, distort reporting, and cause multiple follow-ups to the same prospect.

Data-loss risks:

• If CRM creation succeeds but the Slack or Google Sheet step fails, the workflow may be partially complete.
• If the Google Sheet row is used as the operational log, failed rows may be missing.
• If the form payload is missing a required field, the workflow may fail without a visible failed-lead record.

Duplicate risks:

• no idempotency key
• no CRM search step before create
• no normalized email or phone matching
• no duplicate-handling branch
• no safe behavior for repeated webhook delivery

Retry risks: Zapier retries may repeat create actions unless the workflow checks for an existing record first.

Logging gaps:

• no workflow run status log
• no failed-lead table
• no clear record of partial completion
• no owner field for follow-up

Recommended fixes:

1. Add a CRM search step before creating a new lead.
2. Use normalized email plus source form submission ID as deduplication keys.
3. If an existing lead is found, update it and append an activity note instead of creating a new record.
4. If CRM lookup fails due to timeout, stop the workflow and route the item to a failed-lead review table.
5. Add a final status log that records success, partial success, or failure.
6. Send critical failure alerts to the workflow owner, not only a generic Slack channel.
7. Add a manual recovery process for failed leads.

Fix priority:

1. CRM lookup-before-create logic — immediate.
2. Failed-lead review table — high.
3. Final status logging — high.
4. Owner-specific alerting — high.
5. Google Sheet log cleanup — medium.

Testing checklist:

• submit a valid new lead
• submit duplicate email
• submit duplicate phone number with different formatting
• submit missing phone number
• simulate CRM timeout
• simulate Slack failure
• simulate Google Sheet failure
• confirm no duplicate CRM record is created
• confirm failed items are visible for review
• confirm workflow owner receives actionable alert