Connected tools
Phone checks in your Zaps.
Install QuietPass, connect your own workspace, and add phone formatting, carrier checks, or messaging-app registration to a workflow.
Add phone intelligence between a contact trigger and the next action in your Zap.
Install in Zapier See lookup pricing
Private invitation installation; not App Directory listed.
Install and connect
This invitation gives your Zapier account access to the QuietPass connector. It is a private integration, separate from Zapier's reviewed App Directory.
- Accept the invitation.
Sign in to your own Zapier account and choose Accept Invite & Build a Zap. Search for QuietPass when adding an action.
- Connect your workspace.
Complete QuietPass account setup and activate your balance. Open API keys & usage, create a server API key, and save it. Paste it only into Zapier's QuietPass connection password field. Give the connection a recognizable name. The connection test reads your wallet without purchasing a lookup.
- Keep the Zap off while testing.
Each customer uses their own API key, workspace, and credit. Never put keys in contact fields, table columns, notes, or exports.
Start with free formatting
Add a contact-created or new-row trigger and the Format Phone Number action. Map one phone number and, for national input, its two-letter country code such as US or GB. International + and 00 formats work without a country. Run manually before turning on the Zap.
Editor tests return a clearly marked simulated sample with sample=true; they do not send the mapped number or spend credit. A live Zap run returns sample=false. Use a fictional number such as +12015550123 for a formatting rehearsal.
Add paid checks deliberately
- Quote Phone Lookup.
Map the phone, optional country, checks, and your fixed GBP, USD, or EUR workspace currency. Set Maximum Price per Lookup. Map a stable source event ID such as
crm:contact-123:phone-revision-2. Keep it unchanged on retries; do not use the phone number alone, a run ID, or the current time. Quoting is free. - Check Phone Number.
Place this action immediately after the quote. Map Quote ID, Quoted Maximum in Micros, and Original Request Key from that exact quote step. Allow Live Lookup starts false. Set it true only when you authorize credit use for each matching contact.
- Write a settled result.
Update only your QuietPass result fields after execution succeeds. Keep the Zap off until you have checked one manual run and confirmed the destination mapping.
Quotes expire after five minutes. Do not put delays, human approvals, or long-running actions between quote and execution. Phone checks cost at most 0.02 and messaging apps at most 0.03 in the workspace currency at current package prices; selecting both costs at most 0.05 per number. Definite negative answers are billable; entirely unavailable packages cost zero.
Version 1.0.1 uses the direct quote and execution API. Its per-lookup ceiling and wallet limits apply. The shared saved-operation daily limits in Connected tools do not govern these direct actions; keep the Zap off to stop future runs. A request already sent may finish. Zapier may require a paid plan for multi-step Zaps and charges its own tasks separately; installing this invitation does not upgrade your plan.
Retry the original request
If execution times out, retain the original quote, request key, and maximum. Retry only that failed action, or use Get Phone Lookup Result with the saved quote ID. This recovery action only reads a retained result and never buys another lookup.
Pending, not-started, and expired results stop downstream updates. Do not interpret them as false. Replaying the entire Zap may create a new quote; using it with the old event key is rejected to prevent a second purchase. Recover the original result instead. Results remain available for 24 hours; review expired work before deliberately authorizing a new event.
Keep false and unknown distinct
Map valid, line_type, carrier, sms_supported, whatsapp_registered, and telegram_registered into dedicated result fields. False is a definite negative; null is unavailable. Preserve reason fields and sms_assumed so inferred mobile SMS support remains distinguishable from a direct enablement result. These checks do not guarantee message delivery.
Zap history may contain phone inputs and returned results. Restrict access and configure retention. If a destination write fails, recover the saved result and retry only the write. Include a request ID when asking for help, and keep API keys out of support messages.