Loqate

Verify and standardize postal addresses in 245+ countries with Loqate. Agents autocomplete address capture, cleanse addresses against reference data, validate phone numbers and email addresses, and geocode locations to coordinates.

6 actions API key available

Loqate website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new order lands from the storefront with a customer-typed shipping address

Verify Address cleanses the address against Loqate's reference data and returns an AQI grade and an AVC code

The agent reads the AVC to see whether Loqate fully verified the address or had to change it

Geocode Location attaches coordinates to the verified address for carrier zone routing

Orders that verified cleanly proceed to fulfillment with the standardized address written back

An operations owner reviews the addresses Loqate corrected or could not verify before any label prints

Approved corrections overwrite the shipping record; rejected ones trigger a customer follow-up instead of a parcel

What This Integration Enables

Loqate is reference data with an API in front of it: postal files, geocodes, and telecom registries for 245+ countries, queryable one record at a time. That makes it the natural checkpoint an agent runs every inbound record through before that record is trusted anywhere else. FlowRunner agents verify and standardize postal addresses, validate emails and phone numbers, resolve typeahead address capture, and geocode locations to coordinates, then route each result on the quality metadata Loqate returns rather than on hope. The point is not that verification happens. It is where the decision lands when verification is ambiguous: - Verify Address returns an AQI grade and an AVC code, so agents can branch on evidence: pass clean addresses through, queue rewritten ones for review - Validate Email flags disposable, catch-all, and role-based addresses before they join a list - Validate Phone reports line type and carrier, so a dialer never burns time on a disconnected landline - Geocode Location turns verified addresses into coordinates for territory routing and proximity logic - Every Loqate call is metered, so [human-in-the-loop](/concepts/human-in-the-loop) gates also govern when bulk sweeps are worth the spend

Without FlowRunner

Bad addresses found by the carrier The first system to notice a typo is UPS, and the notice arrives as a returned parcel and a surcharge

Contact data rots on entry Fake emails and dead phone numbers enter the CRM at signup and get discovered at the worst moment, mid-campaign or mid-dunning

One format per country, badly Address fields built for US ZIP codes mangle everything from Japanese blocks to Irish Eircodes

With FlowRunner

Verification at the moment of capture Every address is cleansed and graded before it is stored, with the AVC recording exactly what changed

Contacts checked before they count Emails and phones are validated on the way in, so lists and dialers work from reachable data

Corrections reviewed, not assumed Addresses Loqate had to rewrite queue for a human decision instead of silently replacing what the customer typed

Use Case Scenarios

Checkout addresses verified before the label exists

A [Shopify](/integrations/shopify) order arrives with a shipping address the customer typed on a phone. The agent runs Verify Address with the order's country code and reads the AVC. A fully verified address flows straight to fulfillment with the standardized form written back to the order. An address Loqate corrected, say a premise number it changed, posts to [Slack](/integrations/slack) as a side-by-side: what the customer typed, what Loqate returned, and the AQI grade. The fulfillment lead approves the correction or asks the customer, and only then does the label print. The parcel that would have boomeranged never ships.

Lead intake that filters itself

A [Typeform](/integrations/typeform) submission lands with an email and a phone number. The agent runs Validate Email and Validate Phone in the same pass. A disposable email or an invalid number stops the lead before it reaches [Airtable](/integrations/airtable); a valid pair creates the record with the standardized international phone format and the validation flags stored alongside. Sales calls numbers that ring, and the bounce rate on the next campaign reflects reality instead of form-fill fiction.

Territory routing by coordinates, not guesswork

When a qualified lead enters the pipeline, the agent calls Geocode Location on the company's postal code and country, attaches latitude and longitude to the record, and computes which field rep's territory the point falls in. The assignment posts to [Slack](/integrations/slack) with the map context, and the rep accepts or flags a boundary dispute. Territory arguments become a review step with coordinates attached instead of a weekly spreadsheet fight.

Human-in-Loop Highlight

Verify Address does not just grade an address, it rewrites it, and an approved rewrite becomes the address a physical parcel travels to. When the AVC shows Loqate changed the premise number or could only partially verify a rural route, the corrected address and the customer's original are no longer the same place, and picking wrong means goods on a stranger's porch and a reshipment on your invoice. So FlowRunner agents never let a changed address overwrite the shipping record on their own. The correction queues with both versions, the AQI grade, and the AVC decoded into plain language, and a fulfillment owner decides: accept Loqate's version, keep the customer's, or ask the customer. The same gate scopes bulk work, because a scheduled re-verification sweep across an entire customer table is metered spend that cannot be recalled, and a person approves the batch size before the meter starts.

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

6 actions

Address Capture

Find Address Searches for addresses matching a text query, returning ranked candidates for typeahead and autocomplete. Container candidates such as streets or localities can be drilled into by passing their Id back as the Container parameter.
Retrieve Address Retrieves the complete, structured details of a single address from a Find Address candidate: formatted lines plus discrete components like building number, street, city, postal code, and country. The second step of the capture flow.

Verification

Verify Address Verifies, cleanses, and standardizes a postal address against Loqate's global reference data. Returns the corrected address plus an Address Quality Index grade and an Address Verification Code describing exactly what was verified and changed, with optional geocode. The action this page's human gate exists for.
Validate Phone Validates a phone number and returns its formatting, line type, and reachability details, including number type, detected country and carrier, and standardized international and national formats.
Validate Email Validates an email address for correct syntax, a resolvable domain, and mailbox deliverability. Flags disposable, catch-all, and role-based addresses so lists stay reachable.

Geocoding

Geocode Location Converts a postal code, street, or place name into latitude and longitude with available administrative context. Used to place verified addresses on a map or drive distance and territory calculations.

Frequently Asked Questions

What can FlowRunner do with Loqate?

FlowRunner agents can run Find Address, Retrieve Address, and Verify Address in Loqate, plus 3 more actions.

Does connecting Loqate to FlowRunner require OAuth?

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

Can Loqate trigger a FlowRunner workflow automatically?

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

Start building with Loqate

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

Start Building Free Talk to us