← All integrations
CRM · via Zapier (Webhooks by Zapier)
Veriastra in Salesforce
Routing rules send Leads to people. This adds one step before the routing, so a Lead that cannot be reached at all is labelled rather than assigned — the difference between an SDR's hour and a dead record.
01
Trigger: Salesforce → New Lead
Updated Lead if enrichment happens after creation and you want the final values checked.
02
Action: Webhooks by Zapier → POST
Payload Type JSON. Map Email and Phone from the Lead.
https://veriastra.com/api/screen
{ "purpose": "crm-lead", "email": "{{Email}}", "phone": "{{Phone}}" }03
Filter: only the ones worth stopping for
Filter by Zapier on decision — continue if it *is not* write.
04
Action: Salesforce → Update Record
Write decision to a custom picklist field on the Lead and reasons to a long text field. Assignment rules can then skip discard without anyone reading a report.
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.
- The Zapier path, not an AppExchange package. Nothing is installed in your org and no Salesforce data is stored here.
- Salesforce triggers on Zapier need an edition with API access — Professional and below often do not have it. Check before you build the Zap.
- 1 credit per identifier, capped at 2 per Lead.