Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Before you begin
Choose a stable business reference for the incoming enquiry and decide how your team will handle retries, shared email addresses and multiple Zaps using the same source.
Follow these steps
- Search for a suitable existing lead before creating a new one, then explicitly handle no match and ambiguous matches.
- Record a source enquiry reference in a supported field or in an approved downstream tracking system where appropriate.
- Review all enabled Zaps for overlapping triggers and create actions.
- Add a filter or other approved guard when a Zap can create a lead that another Zap will immediately send back to the source.
- After a timeout or uncertain result, inspect existing CRM and destination records before replaying the action.
Check the result
A repeated source event, an overlapping Zap or an uncertain retry has a defined handling path rather than automatically producing another lead.
If something does not look right
Pause the affected Zaps if duplicate counts rise. Keep the source, CRM lead and Zap run references so support can identify whether the repeat came from a source retry, webhook delivery or another automation.
Fields, rules and limits
- The current Create Lead action does not enforce an idempotency key.
- Search-then-create reduces some duplicates but is not an atomic uniqueness guarantee when requests overlap.
- Webhook events include an event identifier, and delivery attempts include a delivery reference. An integrator can use those references when designing appropriate deduplication.
Questions and answers
Will the CRM reject the same lead twice?
Do not assume it will. This create action does not promise duplicate-email rejection or request idempotency.
Is Find Lead followed by Create Lead completely safe from duplicates?
It helps with ordinary repeats, but two simultaneous runs can both find no match before either creates a record. Use an approved serialisation or deduplication design when uniqueness is essential.
Can two Zaps intentionally receive the same event?
Yes. Each active subscription can receive it. Check for overlapping destination actions before treating a second result as a connector fault.
Can a lead created by Zapier trigger another Zap?
Native lead-created hooks can run after creation, so a connected workflow can produce another new-lead event. Use filters to prevent unwanted feedback loops.
Does a request ID prevent duplicate creation?
A diagnostic request reference is not an idempotency guarantee. Do not rely on resending the same request ID to suppress a second Create Lead action.
Should I delete duplicates automatically?
Review ownership, linked activity and the cause first. Follow your organisation’s authorised record-management procedure instead of adding an untested automatic deletion step.
Useful next steps
- Understand queued events, retries and delays
- Refresh or reconnect an expired connection
- Pause, disconnect or hand over a Zapier workflow
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.