Skip to main content
Enformion looks up US consumer public records for leads who supplied an email address or a supported North American phone number. An inbound caller can be enriched using caller ID alone; an email address is not required. Connect Enformion with your galaxy_ap_name and galaxy_ap_password credentials using Connecting integrations. Both actions are available to agents and scripts through the connected organization’s integration.

​
Look up a person

Supply email, phone, or both; name is optional and cannot identify a person on its own. Phone-only enrichment uses reverse-phone Caller ID. With an email, the lookup verifies contact records against the supplied identifiers and can fall back to email lookup and then reverse-phone lookup. The result reports found and, for a match, matched_on (email or phone). Available details include name, age, address history, phone numbers, and relatives. An email returned for a phone match comes from the provider’s record; Erdo does not invent one. A phone match is evidence tied to that number, not proof that the person speaking currently owns it.

​
Find currently owned properties

Supply an email, or a supported phone number together with the lead’s full name. Optional fallback_name supplies a full name only when name is missing or has fewer than two words. A usable preferred name always wins. The action selects one name before contacting the provider; it does not retry with the fallback after a miss. This lets an automation prefer an accepted enrichment name while retaining the submitted full name as input fallback. Property lookup rejects a phone without a full name before contacting the provider. With phone and full name, Erdo requests a contact record and checks that the record contains that phone and a person ID. It searches properties by that ID and returns only parcels listing that person as a current owner. It never falls back to a name search or uses Caller ID to infer property ownership. found=false means no verified person or currently owned property was found. It does not prove that the person owns no property.

​
Input and result handling

  • Phone inputs require a ten-digit NANP number, optionally prefixed with country code 1; formatting such as spaces, parentheses, and hyphens is accepted.
  • Invalid supplied email addresses are rejected, even when a phone is also supplied.
  • An unsupported optional phone is omitted when a valid email is present, so it does not break the email lookup. Without a valid email or supported phone, the action returns an input error before contacting Enformion. Property lookup also requires a full name when email is absent. Phone-only person enrichment remains available.
  • Provider errors are distinct from found=false; automations should record failures separately from searches that completed without a match.
These records provide context for a lead. They are non-FCRA data and must not be used for eligibility, credit, or tenancy decisions. HTTP failures identify the requested endpoint, search type and response status, with the provider’s error text when present. An empty-body 404 remains a provider request failure; it does not establish that a person or property was not found. Enformion actions have no extra_params input for overriding request fields. Credential failures still require reconnecting the integration; rate limits remain errors rather than no-match results.