Send new lead events to a Zap
Configure and test a New Lead workflow in Pixie CRM, understand queued delivery and avoid assuming historical or every-update coverage.
Before you begin
Use an approved Zapier app that exposes the New Lead trigger. Confirm that the authorising staff account can view all leads and that the destination may receive the mapped lead information.
CRM workspace → Tools → Pixie CRM Automations (or Utilities in a classic layout)
Follow these steps
- Choose New Lead in the approved app and select the correct company connection.
- Follow the app’s trigger test instructions. Sample lead data is for field mapping; loading a sample does not prove a live subscription has delivered an event.
- Configure the destination action and map only the fields it needs.
- Enable the test workflow as directed, then create one uniquely labelled fictional lead through the normal CRM lead workflow.
- Check Zap history and the destination. Record the CRM lead ID and confirm that the expected destination record or notification exists once.
Check the result
The new lead is present in the correct CRM workspace, the Zap run contains that event and the intended destination action is verified.
Rules, fields and operating limits
- Events are captured for authorised active subscriptions; existing leads are not automatically replayed when a subscription is created.
- Delivery is queued and processed by the workspace scheduler, so “instant trigger” does not mean zero latency.
- The technical lead.updated event is not a complete feed of every CRM change. Use only update workflows explicitly agreed and tested for your setup.
If something does not look right
If nothing arrives, check that the Zap is enabled, the connection still works, the subscription exists and processing has had time to run. Use the delivery guide before creating repeated test leads.
Questions and answers
Will connecting send all my old leads?
No. New subscriptions do not automatically backfill the historical lead register. A test sample or a separate approved migration is different from a new-lead event.
Why does the trigger say instant but the event is delayed?
The connector uses a stored queue and scheduled processing. Queue depth, retries, the scheduler and Zapier processing can all affect delivery time.
Does editing a lead fire New Lead again?
New Lead represents creation, not an ordinary edit. Do not use it as a record-update or status-change feed.
Are imported or form-created leads covered?
Supported workflows that call the native lead-created hook can generate events. Test the exact form, importer or external tool you intend to use; do not assume every third-party importer emits that hook.
Can more than one Zap receive the same lead?
Yes. Separate active subscriptions can intentionally receive the same event. Review all enabled Zaps when investigating repeated destination actions.
Does this send emails by itself?
The event sends lead information to its configured Zapier webhook. An email or other external action happens only if the Zap includes and successfully runs that destination step.
Useful next steps
Contact Pixie CRM support. Include the workspace, action, run reference and time; keep credentials private.