Create a CRM lead from a Zap
Map a Zapier action into a Pixie CRM lead, choose valid source and status values and verify the saved record before enabling live intake.
Before you begin
Confirm Create permission for Leads, valid source/status choices and the intended company connection. Use a fictional name and avoid assigning a real colleague until notifications have been considered.
CRM workspace → Tools → Pixie CRM Automations (or Utilities in a classic layout)
Follow these steps
- Choose Create Lead in the approved app and select the company-specific connection.
- Map a non-empty lead name. Map email only when the source provides a valid email address.
- Choose an existing source and status from this workspace. If assigning a staff member, choose an active staff member in the same workspace.
- Map the remaining supported fields deliberately. Keep personal information to what the business workflow needs.
- Run one test. Open Leads in the CRM and check the saved name, contact details, source, status, assignment and activity.
- Before publishing, add the duplicate and loop controls described in this section and agree who will review failed runs.
Check the result
A single lead exists in the intended workspace with the correct mapped fields and a result ID that can be used to investigate the run.
Rules, fields and operating limits
- Name is required and limited to 191 bytes by the current validation; very long multibyte names may reach the limit sooner.
- A supplied email must pass email validation. Assignees must be active staff in this workspace.
- The action creates a private lead. It does not update an existing lead, create a customer or provide automatic create-request deduplication.
If something does not look right
If a test times out, search the CRM before replaying it. The record may already exist. If creator attribution or activity ownership is wrong, pause the pilot and ask support to verify the workflow before live use.
Questions and answers
Can I leave the name blank if I have an email?
No. Provide a meaningful non-empty lead name. Email does not replace the required name.
What happens if source or status is invalid?
The current backend can fall back to an available source or status. Select valid values explicitly and check the saved record; do not use fallback behaviour as your mapping strategy.
Can I assign the lead to someone in a different company?
No. Use an active staff member from the connected workspace. Staff IDs are workspace-local.
Will a test create a real record?
Yes. The Create Lead test is a write operation. Use clearly labelled fictional information and follow your normal authorised test-record cleanup process.
Does assignment notify the staff member?
The action uses the native lead creation workflow, which can invoke normal assignment notifications and activity handling. Test with an appropriate assignment and tell the responsible colleague beforehand.
Does Create Lead update a matching email automatically?
No. A separate Find Lead step can help you branch on existing records, but the current Create Lead action is not an upsert or update action.
Useful next steps
Contact Pixie CRM support. Include the workspace, action, run reference and time; keep credentials private.