Automation Phone Numbers or Email Addresses Are Being Formatted Incorrectly: What to Check
When automation formats phone numbers or email addresses incorrectly, the value was captured but stored or sent in a format the destination rejects. A phone number missing a country code or an email with extra whitespace fails validation downstream. The problem is the normalization, not the capture. Find where the format changes before the value reaches the destination.
Table of Contents
- 01.Why formatting breaks downstream
- 02.What to check first
- 03.Phone number country codes
- 04.Whitespace and punctuation in emails
- 05.Capitalization and duplicate records
- 06.Normalization at the right stage
- 07.Phone formatting and SMS delivery
- 08.How to test it
Why formatting breaks downstream
Phone numbers and email addresses are sensitive to format. A phone number that works in one system may fail in another because of a missing country code, spaces or punctuation. An email with leading whitespace or inconsistent capitalization may be rejected or create duplicate records. The value was captured, but the format it was stored or sent in does not match what the destination expects.
| Field | Problem | What to check |
|---|---|---|
| Phone | Missing country code | Whether the number includes the country prefix |
| Phone | Spaces or punctuation | Whether the destination accepts non-digit characters |
| Leading or trailing whitespace | Whether the value is trimmed before storage | |
| Inconsistent capitalization | Whether the destination treats case as significant |
What to check first
- Compare the phone or email value in the source and the destination.
- Check for whitespace, punctuation or capitalization differences.
- Confirm whether the destination requires a specific format for the field.
- Check whether the automation normalizes the value before sending.
- Review any duplicate records caused by format differences.
Phone number country codes
A phone number without a country code is ambiguous. The destination may assume a default country or reject the number. If the source captures local numbers without a country prefix and the destination expects an international format, the number fails or reaches the wrong region. Confirm whether the destination requires a country code and whether the automation adds one. Do not assume a universal phone format, because every platform and region has its own requirements. Some platforms offer a default country setting that applies when no prefix is present.
Whitespace and punctuation in emails
Email addresses are sensitive to whitespace. A leading or trailing space turns a valid email into an invalid one. Some systems trim whitespace automatically and some do not. If the source captures the email with whitespace and the destination does not trim it, the email fails validation or creates a duplicate that differs by a single space. Confirm the automation trims whitespace before storing or sending the email.
Capitalization and duplicate records
Email capitalization can create duplicate records. Some systems treat uppercase and lowercase emails as the same record and some treat them as different. If the source captures mixed case and the destination is case sensitive, the same person can appear twice. Normalizing emails to lowercase before storage prevents this. Confirm whether the destination is case sensitive and whether the automation normalizes the case.
Normalization at the right stage
Normalization should happen before the value reaches the destination. Trimming whitespace, lowercasing emails and adding country codes are transformations that belong in the automation or the mapping stage. If the destination receives an unnormalized value, it may reject it or store it incorrectly. Add a transformation step that normalizes the value before the destination action. Field mapping problems are covered in the guide on webhook data mapping wrong.
Phone formatting and SMS delivery
Phone formatting affects SMS delivery. A number in the wrong format may fail to send or deliver to the wrong region. If SMS messages are not reaching contacts, check the phone format in the CRM. Confirm the number includes the country code and has no unexpected characters. SMS delivery problems can originate in formatting long before the message is sent.
How to test it
- 1.Submit a test form with a phone number and email in a raw format.
- 2.Check the value as stored in the source and as sent to the destination.
- 3.Look for whitespace, punctuation, capitalization or missing country code.
- 4.Confirm whether the destination accepted or rejected the value.
- 5.Add normalization for whitespace, case and country code as needed.
- 6.Resubmit and confirm the value now arrives in the correct format.
Frequently Asked Questions
Why are my automation phone numbers formatted incorrectly?
The number may be missing a country code, contain spaces or punctuation the destination rejects or be stored in a local format when an international format is required. Confirm the destination's format requirements and normalize the number before sending.
How do I fix email formatting problems in automation?
Trim leading and trailing whitespace and normalize the email to lowercase before storing or sending. This prevents validation failures and duplicate records caused by case or whitespace differences.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Webhook Data Goes Into the Wrong Field: How to Fix Mapping Problems
Wrong field mapping happens when the key does not match the payload or the data type does not match the destination. Capture the actual payload before changing the mapping.
Automation Is Creating Duplicate CRM Contacts: How to Find the Source
Duplicates come from create versus update logic, not the CRM database. Fix the matching in the workflow before you deduplicate the records.
Automation Breaks When a Field Is Empty: How to Handle Missing Data Safely
An empty field is not the error. The error is the workflow not accounting for the possibility that the field would be empty. Handle missing data with explicit branches, meaningful defaults or skipped steps.