Zapier & API — Stricter Create Person validation

What We Fixed

Previously, the Zapier “Create Person” action let you save Zaps with every field blank, which could fail silently at run time or quietly create empty contact records.

Changes

• Zapier: The Create Person action now clearly documents that Full Name and at least one contact method (Email or Phone) are required. The action will return a clear error if any of these are missing.
• Partner API / Make.com / Zapier: Server-side validation now applies a consistent floor. POST /api/partner/people, POST /api/make/actions/people, and POST /api/zapier/actions/people return a clear 422 error when a name or contact method is missing, instead of creating an empty record.

What You Need to Do

Any integration that was creating nameless or contactless records will need to map a Full Name plus at least one email address or phone number going forward. Failing Zap runs will surface the validation error in your Zap history.

Thank you to the users who reported this!