DQE
Analytics & DataValidate and correct email addresses, landline and mobile numbers, and international postal addresses in real time with DQE. Agents fix contact data at the point of capture rather than after a campaign fails.
What This Integration Enables
Most validators in this category tell you whether a value is good. DQE's design goes a step past that: it proposes the corrected value. Validate Email Address inspects syntax and domain, optionally probes the mailbox name, and when correction is requested and something is wrong, returns a proposed replacement address. Validate Phone Number reformats the number into the requested style and reports the assigned operator, the previous operator where the number has been ported, the geographic location it was originally allocated to and the line type, with an activity check available where the operator exposes reachability. Validate Postal Address takes a whole captured address and hands back the standardized street, postal code, city, state and country with coordinates. Correction is the product, not a side effect.
That posture is also what makes DQE unusually opinionated about how you call it. Validate Email Address is documented as a real-time single-record endpoint that must not be used for batch processing. Validate Postal Address requires its input in a strict pipe-separated layout where every pipe is present even when a section is empty. Validate Phone Number's verdict is three-way rather than binary: 1 means valid and attributed to an operator, 2 means the syntax is valid but nothing more can be said, and 0 means invalid. Building agents on top of that means honouring the middle verdict rather than rounding it to a pass or a fail. Address capture is offered both as a one-field autocomplete and as a guided funnel from postal code to city to street to the exact building complement, in more than one country, with extended matching on as few as two digits for France and Belgium. Company data completes the set: Search Companies By Name and Search Companies By Registration Number both return the standardized name and address, VAT number, registration numbers, legal structure, activity classification, incorporation date and staff and turnover where known. This is the layer Orchestration as a Service needs underneath it, because an agent can only be trusted with a decision when the fields it is deciding on are real.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Confirming the legal entity before a quote goes out
A quote request arrives from a trading name. Before anything is priced, the agent calls Search Companies By Name and reads back the standardized company name, address, VAT number, SIREN and NIC, legal structure, activity classification, incorporation date and staff count. Where the form supplied a registration number instead, Search Companies By Registration Number confirms the entity behind it directly. The resolved record is written into NetSuite as the customer of record, so the quote, the contract and the invoice all name the same legal entity rather than three variations of a brand.
One-field address capture across borders
A form asks for an address in a single box. The agent calls Search Addresses with whatever has been typed and returns up to twenty ranked suggestions, each parsed into postal code, city, street, street type and number, carrying the identifier needed to fetch building complements. When the user picks one, Get Address Complements lists the buildings, staircases and apartments registered at that number, so the unit is chosen from a validated list rather than typed. For flows that prefer a stepped experience, the same data drives the guided funnel: Search Postcodes And Cities, then Search Streets In City, then Autocomplete Address Complement.
Cleansing address records that were never validated
An inherited customer table holds addresses captured before any validation existed. A scheduled flow reads them in batches, assembles each one into the pipe-separated layout Validate Postal Address expects, and writes back the standardized street, postal code, city, state, country and coordinates. Records that come back unresolvable are not deleted and not silently altered. They are collected into a worklist and posted to the data owner in Microsoft Teams with the original value alongside, because an address that cannot be standardized is often a real place with an unusual form rather than a mistake.
Human-in-Loop Highlight
The gate on DQE sits exactly where its strength is. When Validate Email Address finds a wrong syntax or domain and correction is enabled, it returns a proposed replacement address, and that proposal is almost always right. Almost always is the problem. The email address on an account of record is where invoices, contracts and password resets go. Replacing what a customer typed with what an algorithm inferred, silently, means that when the inference is wrong the customer stops receiving anything from you and has no way to know why. The failure is invisible from both sides. So the agent draws a line by field ownership rather than by confidence: it applies address standardization and phone reformatting on its own, because those normalize a value without changing where anything is sent, and it stops on any proposed change to an email address that a person supplied. The message reads: "Quote request 2210 from Cabinet Lefevre. Submitted j.lefevre@cabinet-lefevr.fr, verdict invalid domain, proposed j.lefevre@cabinet-lefevre.fr. Send the quote to the proposal, send to the original, or ask the customer?" A person answers in the channel and the agent resumes with the original value preserved on the record either way. The same rule covers the phone verdict of 2, valid syntax only: it is neither a pass nor a fail, so the agent treats it as a question rather than inventing an answer.
Agent Capabilities
11 actions- Validate Email Address Checks a single address in real time and returns its validity state, inspecting syntax and domain and optionally probing the mailbox name. When correction is requested and the syntax or domain is wrong, a corrected address is proposed. Designed for single-record real-time calls and not to be used for batch processing.
- Suggest Email Addresses Builds a ranked list of plausible addresses for a person from their first name, last name and whatever has been typed so far, with the syntax verdict for the partial input. Used to power assisted entry on sign-up and checkout forms so the typo never happens.
Phone
1- Validate Phone Number Validates a landline or mobile number for a given country and returns it reformatted in the requested style, with the assigned operator, the previous operator where the number has been ported, the geographic location it was originally allocated to and the line type. The verdict is three-way: 1 for valid and attributed, 2 for valid syntax only, 0 for invalid or non-existing. Activity checking can be enabled to add reachability where the operator exposes it.
Address Validation and Capture
6- Validate Postal Address Verifies and normalizes a complete captured address, correcting formatting and returning standardized street, postal code, city, state and country with coordinates where available. Takes a whole address rather than a partial one, which makes it the right action for cleansing existing CRM or ERP records. The address parameter uses a strict pipe-separated layout in which every pipe must be present even when a section is empty.
- Search Addresses Returns ranked suggestions from a single free-form line of input, which is what drives one-field address autocomplete. Each suggestion carries the parsed postal code, city, street, street type and number plus the street identifier used to fetch complements. Up to twenty suggestions per call.
- Get Address Complements Retrieves the building, staircase and apartment complements registered at a specific street number, using the street identifier from Search Addresses, and returns the geolocation of the building. Used as the closing step of a capture flow so the user picks their exact unit from a validated list.
- Autocomplete Address Complement Suggests building and apartment complements for a street number while the user is still typing, closing the guided funnel that begins with Search Postcodes And Cities and continues with Search Streets In City.
- Search Postcodes And Cities Finds localities from a postal code or a city name and opens the guided funnel. Each result carries the postal code, city, administrative area, coordinates and the city identifier the street step needs. Extended search lets France and Belgium match on as few as two digits, and a filter narrows results to postal codes only, postal codes with streets, or postal codes with post office boxes.
- Search Streets In City Suggests streets inside a locality already selected through Search Postcodes And Cities, returning matching streets with the street identifier used to look up number complements.
Company Data
2- Search Companies By Name Returns matching companies for a business name, which is what powers company autocomplete on B2B sign-up and quote forms. Each suggestion carries the standardized name, address lines, postal code and city, VAT number, registration numbers, legal structure and activity classification, incorporation date, and staff count and turnover where known. Used when the customer knows the trading name but not the registration number.
- Search Companies By Registration Number Returns the companies matching an official registration number such as a SIREN or SIRET, with the same record a name search produces. Used when a registration number was captured on a form or imported from another system and the legal entity behind it has to be confirmed before an account, quote or invoice is created.
Frequently Asked Questions
What can FlowRunner do with DQE?
FlowRunner agents can run Validate Email Address, Suggest Email Addresses, and Validate Phone Number in DQE, plus 8 more actions.
Does connecting DQE to FlowRunner require OAuth?
No. DQE connects to FlowRunner with an API key, no OAuth flow required.
Can DQE trigger a FlowRunner workflow automatically?
DQE doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DQE
$100 in credits. No card required. Connect in minutes.