Find a lead before taking action
Search Pixie CRM leads by email, phone or text from an approved Zapier workflow and handle missing or multiple matches deliberately.
Before you begin
Confirm Global View permission for Leads and decide what constitutes a reliable match. An email or phone number can be shared or duplicated, so a search result is not proof of identity.
CRM workspace → Tools → Pixie CRM Automations (or Utilities in a classic layout)
Follow these steps
- Choose Find Lead or the supported search step in the approved app.
- Start with one specific search value, such as the complete email address. Phone matching uses the stored text, including formatting.
- Run the search and inspect the returned lead ID, name and contact details in the correct workspace.
- Define separate paths for no match, one verified match and multiple possible matches.
- If your approved app provides find-or-create behaviour, check that its create branch maps the required name and does not blindly create on a search error.
Check the result
The workflow selects a verified CRM lead or intentionally stops for review. An empty result and a failed search are treated differently.
Rules, fields and operating limits
- The API supports exact email and phone comparisons plus a text query across name, company and email.
- When multiple search parameters are supplied, the current backend combines them as alternatives (OR), not a strict all-fields match.
- Search returns at most 20 results, ordered by descending lead ID. An empty search returns no rows.
If something does not look right
For no match, compare spelling and phone format with the CRM record. For ambiguous matches, narrow the query or send the case to review rather than selecting a person solely because they appear first.
Questions and answers
Why does a phone search miss an existing lead?
The stored phone text may include a different country prefix, spaces or punctuation. The current search does not normalise numbers into a common international format.
Does email plus phone mean both must match?
No. Supplying both can return a lead matching either value. Use one reliable value first and verify the returned record.
What if more than one lead has the same email?
Treat the result as ambiguous and review it. Shared inboxes and duplicate records make email alone unsuitable as a guaranteed unique person identifier.
Can a search create or change a lead?
The search endpoint is read-only. A separate configured action can create a record; inspect your Zap’s branches before testing.
Why can I not see every possible match?
The current search response is limited to 20 records. Use a more specific search rather than treating it as a full data export.
Should I create a lead whenever the search errors?
No. An error is not “no match”. Stop and resolve the error, otherwise a temporary connection problem can produce duplicates.
Useful next steps
Contact Pixie CRM support. Include the workspace, action, run reference and time; keep credentials private.