How to build Zapier workflow to route web leads

Recommendation:
Use Zapier with a reliable form trigger (preferably a webhook or the form app’s native “New Submission” trigger), normalize and filter data up front, then use a Salesforce “Find Record / Upsert” pattern to de-duplicate and either update or create the lead. Finish with Slack notifications for both success and error conditions. Add logging and alerting so failures are visible immediately.

Decision criteria (pick approach based on these):
- Volume: if <10k tasks/month Zapier is fine; if very high volume or tight API SLAs, consider middleware or direct API integration.
- Real-time vs batch: Zapier is good for near-real-time; if you need guaranteed ordering/batching, use a queueing approach.
- Skill level: no-code Zapier flows work for most teams; if you need complex dedupe rules, expect to use Code by Zapier or developer help.
- Salesforce setup: if you can mark Email (or another field) as External ID, use Upsert to avoid duplicates at the DB level.

Best-for / Avoid-if
- Best for: small-to-medium teams needing fast implementation, multi-app routing, territory-based Slack alerts.
- Avoid if: very high lead volume (task costs or API rate limits), or if you need strict transactional guarantees.

Practical checklist (step-by-step):
1) Trigger: Use “Webhook by Zapier – Catch Hook” if your form supports webhooks; otherwise use the form app’s “New Submission” trigger (Typeform, Gravity Forms, HubSpot, etc.).
2) Normalize: Add Formatter steps (Text → Lowercase for email; Numbers/Replace to strip characters from phone; Date formatting if needed). Consider a small “Code by Zapier” step for libphonenumber validation if accurate phone parsing is required.
3) Filter: Reject obvious garbage/test leads (Filter: Email contains test OR domain internal), and require required fields (email OR phone). Early rejection saves tasks and API calls.
4) Enrichment/Validation (optional): Use APIs or a quick lookup to enrich company data or validate email/phone.
5) De-duplicate / Upsert to Salesforce:
- Preferred: Use Salesforce Upsert with an External ID (email or custom extId). This lets Salesforce enforce uniqueness.
- If Upsert isn’t possible: Use “Find Record (Lead)” with matching fields (email, phone, company). If found → Update Lead. If not → Create Lead.
6) Routing: Use Paths or Filter steps to route by territory/owner rules (country, ZIP, product). Each path ends with assigning OwnerId in the Salesforce Update/Create action.
7) Notification: Post to Slack channel or individual via Slack action with lead summary and link to Salesforce record. Create two different Slack messages: “New Assigned Lead” for reps and “Lead Delivery Failure” for ops.
8) Logging & retry: Add a “Log” step (Google Sheets or Storage by Zapier) to append each submission and outcome. On errors, send a Slack DM to the ops channel and append the payload to a “failed” sheet.
9) Throttling/spike protection: If you expect bursts, add “Delay For” or queue to smooth calls and reduce Salesforce API errors.

Error-handling tips:
- Use Zapier’s built-in task history and enable email alerts for Zap failures.
- Implement retry logic: for transient Salesforce errors, let Zapier auto-retry (enable Replay or use Zapier Manager to auto-replay failed runs). Record failures for manual review.
- Add clear Slack error notifications with the payload and error message so ops can triage quickly.
- Prevent duplicates at source if possible (form validation, reCAPTCHA, honeypot fields).

Notes on cost and scale: if your lead volume is large, Zapier task counts and Salesforce API limits become the primary constraints—budget for higher Zapier tiers or move to an integration platform / serverless function. For quick wins, the above Zapier pattern will get you reliable routing and dedupe within hours.

Helpful tool: Use Zapier (Webhook or native form triggers) to orchestrate the flow and Upsert into Salesforce for best dedupe results.

Compare Zapier and Make