Veriastra in Pipedrive
The decision belongs before the record, not after it. This connects Pipedrive's New Person trigger to /api/screen, so a lead arrives already answered as write, write-flagged or discard, and your reps never open a person nobody can reach.
Trigger: Pipedrive → New Person
Use Updated Person instead if leads are enriched after creation and you want the check on the final values.
Action: Webhooks by Zapier → POST
Payload Type JSON. Add purpose as a plain value and map email and phone from the trigger.
https://veriastra.com/api/screen
{ "purpose": "crm-lead", "email": "{{email}}", "phone": "{{phone}}" }Filter: only continue when it matters
Add Filter by Zapier on the response field decision — continue if it *is not* write. The clean majority stops here and costs you nothing further.
Action: Pipedrive → Update Person
Write decision into a custom field and reasons into a note, so the rep sees why. Route discard to a Lost label rather than deleting; a record you cannot explain later is worse than one you can.
Before you rely on it
- Your API key goes in the Authorization header as `Bearer ol_live_…`. Create one in the dashboard under API Keys. Never put it in a URL — anything in a URL ends up in logs.
- This is the Zapier path, not a Pipedrive marketplace app. Nothing to install on the Pipedrive side, and nothing of yours is stored here.
- A screen costs 1 credit per identifier you send, capped at 2. Sending both email and phone on every new person is 2 credits per person.
- Zapier's Webhooks action needs a paid Zapier plan. That is Zapier's limit, not ours.