Veriphone
Analytics & DataValidate, format, and look up carriers for phone numbers worldwide with the Veriphone API, checking against national numbering plans. Agents confirm a number is reachable before a message is sent.
What This Integration Enables
Veriphone's distinguishing feature is that it does not treat a phone lookup as one thing. Verify Phone Number offers two tiers. A Standard lookup costs one credit and reports the carrier the number was originally allocated to. A Current Carrier lookup costs ten and resolves the carrier and line type serving the number right now from national portability registries, flagging the number as ported. That distinction matters everywhere a number has changed networks, which in most consumer markets is a large minority of them. Get Current Carrier Coverage exists so an agent can check whether portability data is even available for a country before it spends the ten-credit lookup, and Get Account Credits exposes the balance, plan limit, renewal day and a usage split between the two tiers so an automation can guard itself.
The second half of the connector is a full asynchronous batch pipeline, and it runs in four stages. Upload a CSV of up to 100 MB and a million rows from a publicly accessible URL. Confirm the detected column and row count against the sample values returned. Start the job and poll until the status reports completed. Download the annotated results into FlowRunner file storage as a URL later steps can read. Uploads can also be listed, inspected for their valid, invalid, billable and syntax-error tallies, and permanently deleted. One constraint shapes every design decision on top of it, and it is stated plainly in the API: bulk jobs run Standard lookups only. The batch pipeline cannot see portability. Build for that and the connector is excellent. Ignore it and the batch will confidently mislabel your most-moved customers.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Confirming carrier before one-time-passcode traffic
Passcode delivery fails silently and expensively when a message routes to a carrier the number left. Before an account recovery flow sends a code, the agent calls Get Current Carrier Coverage once to confirm the country supports portability lookups, then runs a Current Carrier lookup on the number. If the response flags the number as ported, the agent uses the current carrier and line type to pick the route through Twilio instead of the allocated one. Ten credits on a passcode is cheap next to a locked-out customer opening a ticket.
Scheduled hygiene on a large messaging audience
A marketing operations team runs a monthly pass over the SMS audience. The agent exports the audience, calls Upload Phone Number File, and reads back the detected row count and two sample values from the selected column, which is the checkpoint that catches a shifted header or the wrong column before a million rows are billed. It checks the balance with Get Account Credits, starts the job, polls until completed, and downloads the annotated CSV. The tallies get written into PostgreSQL so the trend is visible month over month rather than existing only in one file.
Screening non-geographic numbers as a fraud signal
A signup flow verifies each number once and reads the line type. VoIP and non-geographic numbers are not blocked, because plenty of legitimate people use them, but they are scored: the record gets a flag, the account starts at a lower trust tier, and the signal joins the other risk inputs feeding review in Customer.io. The line type is treated as one input to a judgment, not as the judgment.
Human-in-Loop Highlight
Nothing here is more tempting than acting on a finished batch, which is why that is the one place the agent stops. A bulk run comes back with an invalid tally, and the obvious next step is to suppress or delete those rows. The agent will not do it, and the reason is specific to Veriphone rather than generic caution: bulk jobs run Standard lookups only, and Standard lookups report the originally allocated carrier without portability awareness. A customer who moved networks can be described by evidence the batch was never able to gather. Purging on that verdict means deleting real, reachable, paying customers, and the purge is not reversible from the results file. So the agent stops: "Bulk run 4471 finished. 812,400 rows billable, 9,140 invalid, 213 syntax errors. 1,905 of the invalid rows belong to contacts who received a delivered message from us in the last 90 days. Suppress all invalid rows, suppress only those with no delivery history, or re-check the 1,905 individually with Current Carrier lookups first?" A person picks. Delete Uploaded File runs only after that decision is made and the results are stored, because it permanently removes the upload together with its verification results and cannot be undone. That is human-in-the-loop placed where the irreversible step actually is, not bolted onto the front of the job.
Agent Capabilities
10 actionsVerification
2- Verify Phone Number Validates a single number and returns line type, carrier, geographic region, country and formatted variants in E.164, international and local form. Standard lookups report the originally allocated carrier and cost one credit. Current Carrier lookups additionally resolve the carrier and line type serving the number now from national portability registries, flag ported numbers, and cost ten credits. Covers over 240 countries.
- Get Current Carrier Coverage Returns the countries where portability-aware Current Carrier lookups are available, as ISO country codes with a coverage flag and the date the list was last updated. Called before spending ten-credit lookups on a country that may not support them.
Account
1- Get Account Credits Returns the balance and usage for the API key in use, including remaining credits, pay-as-you-go balance, plan name and limit, renewal day, last reset timestamp and a usage breakdown split between Standard and Current Carrier lookups. Used to guard a flow against running out mid-job.
Bulk Verification
7- Upload Phone Number File Uploads a CSV of phone numbers from a publicly accessible URL, up to 100 MB and one million rows. Returns an upload ID plus the detected row count and two sample values from the selected column, which is the checkpoint for confirming the column and header offset before any verification is started.
- Start Bulk Verification Starts a background job verifying every number in a previously uploaded file. Bulk jobs run Standard lookups only, so the results carry no portability awareness. Returns immediately and fails if the account has insufficient credits.
- Get Bulk Verification Status Returns the current processing status of an upload as new, ready, verifying, completed or deleted. Polled after starting a job and confirmed as completed before results are downloaded.
- List Uploaded Files Lists every non-deleted upload on the account, newest first, with ID, original file name, status, size, creation date, column and header configuration, and once verification has run, the counts of billable, valid, invalid and syntax-error rows. Used to find an upload ID or to report on completed runs.
- Get Uploaded File Returns the full detail record for a single upload including processing status and stage, row counts and the verification tallies. Returns an empty object when the upload does not exist or belongs to another account.
- Download Bulk Results Downloads the verified results CSV and stores it in FlowRunner file storage, returning a URL later steps can read. If verification has not produced results yet the original uploaded file is returned instead, so the status is confirmed as completed first.
- Delete Uploaded File Permanently deletes an upload together with its verification results. This cannot be undone, so the results are downloaded and the suppression decision is made before it runs.
Frequently Asked Questions
What can FlowRunner do with Veriphone?
FlowRunner agents can run Verify Phone Number, Get Account Credits, and Get Current Carrier Coverage in Veriphone, plus 7 more actions.
Does connecting Veriphone to FlowRunner require OAuth?
No. Veriphone connects to FlowRunner with an API key, no OAuth flow required.
Can Veriphone trigger a FlowRunner workflow automatically?
Veriphone doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Veriphone
$100 in credits. No card required. Connect in minutes.