Zapier ・ E.164 phone cleanup ・ Apify app
How to use Phone Number Validator in Zapier
Direct answer. To validate and normalize phone numbers to E.164 in Zapier without a carrier-lookup API key, run Apify Actor taroyamada/phone-number-validator via Apify’s Zapier app: trigger on Finished Actor run, then Fetch dataset items, and map international/national formats into Sheets or your CRM. Validation is offline libphonenumber.
Open Phone Number Validator Input on Apify Store
Last updated: 2026-10-30 (Asia/Tokyo). Integration steps verified on Apify docs and the Actor Store listing the same day.
What this Zap does
Zapier reacts when a validation run finishes, then writes structured phone rows (region, E.164, line-type signals when available, validation status) to Sheets or a CRM. It validates formats offline; it is not Contact Details Extractor (page crawl).
| Piece | Role |
|---|---|
| Zapier Apify app | Official Apify integration (docs.apify.com/platform/integrations/zapier) |
| Actor | taroyamada/phone-number-validator — phone strings → format rows |
| First proof input | Leave prefilled numbers +14155552671; defaultCountry US; dryRun false |
| Useful fields | E.164, international, national formats, country/calling code, line classification, validation status |
Connect Apify with Zapier
- Create a Zap. Choose Apify as the trigger or action.
- Connect to Apify → Allow Access.
- Use Test Trigger after you have at least one Console run.
Cleanup path: Finished Actor run → Sheets
- Trigger: Apify Finished Actor run. Select
taroyamada/phone-number-validator. - Add Apify Fetch dataset items for the finished run’s default dataset.
- Add Google Sheets (or HubSpot). Map E.164, national format, country, and validation status.
- Publish. Start the Actor from Console or from a Zap Run Actor step with your number list.
Optional: start a one-number proof from Zapier
- Action: Apify Run Actor. Select the same Actor.
- Prefer async + Finished trigger — Zapier sync has a hard 30 second timeout.
{
"numbers": ["+14155552671"],
"defaultCountry": "US",
"delivery": "dataset",
"dryRun": false
}
Paste up to 1–1,000 user-supplied numbers per the Store input after one row is useful.
Not this path
- Not a live carrier HLR lookup product beyond what the listing documents for offline libphonenumber signals.
- Not Contact Details Extractor page crawling.
- Do not invent unpublished input aliases; use the Store Input schema.
- Never edit the Actor on Apify from this guide; read-only Store usage only.
Related pages
- Bulk Phone Format Validator landing
- TED + SAM bid alerts in Zapier
- Contact Details Extractor in Make
- Contact Details Extractor landing
- Tools catalog
Pricing and input from apify.com/taroyamada/phone-number-validator on 2026-10-30 (Asia/Tokyo). Zapier steps from Apify docs.