Byteplant

Validate postal addresses, email addresses, and phone numbers with Byteplant's three verification services in one connector. Agents standardize and correct contact data before it reaches a CRM or a shipping system.

8 actions API key available

Platform Documentation ↗ Capability data verified 2026-07-31

A quarterly hygiene flow exports every shipping address of record for active customers

Agent calls Submit Address Bulk Validation with the export and records the task id it returns

Agent collects the finished results from the Notify URL callback, since the API exposes no polling endpoint

Agent groups the SUSPECT rows by what the correction actually changed: unit number, street suffix, city, or postal code

Agent re-runs Validate Address on a sample from each group to confirm the correction holds on its own

Agent posts each group into the logistics channel with counts and worked examples

The logistics owner approves which classes of correction may be written back to the address of record

What This Integration Enables

Byteplant is not one validator, it is three, and the connector is honest about that. Address Validator, Email Validator and Phone Validator are separately subscribed products with separate API keys, each configured on its own item, and each powering the actions in its matching category. An action fails with a clear message if its product key is missing. That structure is worth understanding before you design a flow, because it means you can adopt one module now and add the others later without touching the integration, and because the three products return genuinely different verdict vocabularies. Addresses come back VALID, SUSPECT or INVALID. Emails come back as numeric result codes where 200, 207 and 215 are valid, 114, 313 and 314 are temporary and worth a retry, and 3xx and 4xx are unusable. Phones come back VALID_CONFIRMED, VALID_UNCONFIRMED or INVALID with a line type.

The SUSPECT verdict is the one that shapes agent design. It does not mean invalid. It means the address as given is incorrect and Byteplant is supplying a corrected version, which puts a decision in front of the workflow rather than a fact. Alongside the real-time actions, each product exposes an asynchronous bulk path that accepts up to 100,000 rows of CSV and returns a task id immediately, with completion announced by email and by an optional HTTP callback. There is no polling endpoint, so a flow that submits a batch has to be built to receive the result rather than to wait for it. Address coverage runs to more than 240 countries with optional rooftop geocoding, and Search Addresses plus Retrieve Address Details give a form the predictive autocomplete that stops most bad addresses from being typed at all.

Without FlowRunner

Failed deliveries pay for the audit The address problem is discovered by the carrier, and the return shipping is the invoice

Three tools, three integrations Address, email and phone validation each arrive with their own connector and their own credentials to manage

Corrections applied or ignored wholesale Either nothing gets fixed, or a bulk update rewrites addresses nobody looked at

With FlowRunner

Failures caught before the label Deliverability is settled while the order is still on screen

Three products, one connector Address, email and phone validation share one integration surface with per-product keys

Corrections applied by class Each kind of change is reviewed once as a class, then applied to every record it fits

Use Case Scenarios

Correcting the shipping address while the order is still on screen

A checkout uses Search Addresses to autocomplete as the customer types, then Retrieve Address Details to expand the suggestion they picked into a full standardized address. Because autocomplete results come back UNVERIFIED, the agent follows with Validate Address to get an actual deliverability verdict, reading the residential delivery indicator and the address type so a business shipment is not routed to a P.O. Box. VALID addresses pass straight into ShipStation. SUSPECT addresses show the customer the corrected version and let them confirm it, which is the cheapest possible moment to fix an address.

Protecting sender reputation before a campaign

Before a large send, the agent runs Validate Email Address across the new portion of the list. The check is end to end without sending a message: syntax, DNS and MX lookup, misspelled domain detection, disposable and role address detection, an SMTP connection and mailbox existence check, catch-all testing and greylisting detection. Codes in the 3xx and 4xx ranges are removed from the audience in Klaviyo. Codes 114, 313 and 314 are not removed, because they are temporary, and the agent schedules a re-check instead of destroying a good subscriber over a mail server that was busy.

Scrubbing a dialing list before the SMS spend

Ahead of an SMS or call campaign the agent runs Validate Phone Number in extensive mode, which performs a full network lookup rather than the static checks of express mode. It reads the line type and drops premium rate, pager and voicemail numbers out of the send, splits fixed lines from mobiles so the SMS budget is only spent where a text can land, and stores the carrier codes on the record. Numbers returning VALID_UNCONFIRMED are held as automation exceptions rather than being treated as either good or dead.

Human-in-Loop Highlight

SUSPECT is not a failure verdict, and that is what makes the write-back after a bulk address scrub the moment this connector needs a person. A quarterly run over 100,000 customer addresses comes back with thousands of rows marked SUSPECT, each carrying a corrected version that is usually right. Applying all of them automatically means quietly rewriting where a customer's parcels go, at scale, based on a verdict that by definition says the input did not match cleanly. Some of those corrections are a missing street suffix and are safe. Some move an apartment number, or replace a city, and the customer never agreed to it. So the agent does not decide one by one and it does not decide all at once. It groups the corrections by what changed, re-validates a sample from each group so the class is judged on evidence, and puts the classes in front of the person who owns fulfilment: "4,112 SUSPECT rows. 2,890 add or normalize a street suffix. 780 correct a postal code against the city. 388 change or remove a unit number. 54 change the city itself. Which classes should I write back to the address of record, and which should go to the customer for confirmation on their next order?" One review, applied consistently, with the 54 riskiest never touched by an agent. The bulk job is also where the connector's asynchrony matters: results arrive by callback and cannot be polled, so the approval step is built around the callback rather than a wait loop.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Address Validation

Validate Address Verifies and standardizes a single postal address in more than 240 countries and returns a deliverability verdict of VALID, SUSPECT with a corrected version supplied, or INVALID. Returns the address reformatted to local postal standards with district, county, state, address type, a residential delivery indicator, diagnostics and correction hints, plus optional rooftop coordinates when geocoding is enabled.
Search Addresses Returns predictive suggestions for a partially typed address, which is what powers autocomplete in a form. Each suggestion carries an id for Retrieve Address Details. Results are UNVERIFIED, so Validate Address still runs afterwards when a deliverability verdict is required.
Retrieve Address Details Expands a suggestion id from Search Addresses into the full standardized address including street, number, postal code, city, district, county, state, country and address type, plus optional rooftop coordinates. Completes the autocomplete flow once the user picks a suggestion.
Submit Address Bulk Validation Uploads up to 100,000 addresses as CSV for asynchronous batch verification and returns a task id immediately. Processing runs on Byteplant servers and completion is announced by email and, when a Notify URL is supplied, by an HTTP callback carrying the task id. Results are collected from the callback or the account dashboard, since the API exposes no polling endpoint.

Email Validation

Validate Email Address Runs an end-to-end deliverability check on a single address without sending a message: syntax, DNS and MX lookup, misspelled domain detection, disposable and role address detection, SMTP connection and mailbox existence checking, catch-all testing and greylisting detection. Returns a numeric result code with short and full descriptions plus a freemail flag.
Submit Email Bulk Validation Uploads up to 100,000 addresses as CSV for asynchronous list cleaning and returns a task id immediately. Express mode retries temporarily unavailable mail servers for 2 hours and extensive mode for 72 hours. Completion is announced by email and by an optional HTTP callback, with no polling endpoint exposed.

Phone Validation

Validate Phone Number Verifies a single number across more than 240 countries and returns VALID_CONFIRMED, VALID_UNCONFIRMED or INVALID with the line type, geographic location, country code, standardized national and international formats and the carrier codes. Extensive mode performs a full network lookup while express mode runs static checks only.
Submit Phone Bulk Validation Uploads up to 100,000 numbers as CSV for asynchronous batch cleaning and returns a task id immediately. Used to scrub an existing contact database ahead of an SMS or call campaign. Completion is announced by email and by an optional HTTP callback, with no polling endpoint exposed.

Frequently Asked Questions

What can FlowRunner do with Byteplant?

FlowRunner agents can run Validate Address, Search Addresses, and Retrieve Address Details in Byteplant, plus 5 more actions.

Does connecting Byteplant to FlowRunner require OAuth?

No. Byteplant connects to FlowRunner with an API key, no OAuth flow required.

Can Byteplant trigger a FlowRunner workflow automatically?

Byteplant doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Byteplant

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us