TexAu action

Normalize Phone Number (Utility)

Normalizes and validates a phone number to E.164, national, and RFC3966 formats with country metadata.

Texau logoTexAu
texau-normalize-phone-number
enrichmentReturns in secondsLight tier
Input

What it needs.

Map each field to a column in your table. Optional fields can stay empty.

FieldType
  • mobile_number
    The phone number to normalize, as entered by the user.
    text

When to use this.

The Normalize Phone Number action utilizes TexAu's normalize-phone-number API to standardize and validate phone numbers across multiple formats, including E.164, national, and RFC3966. By inputting a phone number as a text parameter, users can obtain essential metadata such as country code, region, and validity status. The output includes fields like can_be_internationally_dialed (boolean), country_code (countryCode), and various phone formats (e164_format, international_format, national_format, rfc3966_format), along with indicators for validity and parsing success. This action is particularly useful for businesses needing to enrich customer contact data, ensuring accurate communication and compliance with international dialing standards. It falls under the enrichment category, making it ideal for applications in customer relationship management (CRM), marketing automation, and data validation processes.

Output

What it returns.

Every field this action writes back to the row. Click a line to expand nested objects.

FieldType
  • can_be_internationally_dialed
    Can Be Internationally Dialed
    nullableboolean
  • country_code
    Country Code
    number
  • e164_format
    E164 Format
    nullabletext
  • international_format
    International Format
    nullabletext
  • is_possible
    Is Possible
    nullableboolean
  • is_valid
    Is Valid
    boolean
  • national_format
    National Format
    nullabletext
  • number_type
    Number Type
    nullabletext
  • region_code
    Region Code
    nullabletext
  • rfc3966_format
    Rfc3966 Format
    nullabletext
  • successfully_parsed
    Successfully Parsed
    nullableboolean
Workflow

How this fits a workflow.

Trigger → Normalize Phone Number (Utility) → enrich → push to your CRM. You set it up once; after that it runs without you.

  1. Step 1TriggerNew row, form submit, or schedule.
  2. Step 2Normalize Phone Number (Utility)The TexAu action runs.
  3. Step 3EnrichWaterfall fills missing fields.
  4. Step 4Push to CRMHubSpot / Pipedrive / Zoho CRM / GoHighLevel.

Two actions you can chain after this one:

Normalize Phone Number (Utility)Remove Extra Whitespace (Utility)Identify Email Type (Utility)
Reliability

Throughput & reliability.

How fast it drains a table, and what happens when the upstream provider has a bad day.

  • Per-minute limit1000 / min
  • Per-day limit1,000,000 / day
  • RetriesAutomatic w/ backoff
  • Failed lookupsZero credits

Who runs this

GTM EngineerRevOpsAgency

Light tier. See pricing; per-action credit cost is private.

FAQ.

Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.

No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.

No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.

HubSpot, Pipedrive, Zoho, and GoHighLevel are bidirectional, with Salesforce coming soon. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Normalize Phone Number (Utility) in 60 seconds.

Connect the account, drop the action on a column, run it on your rows.