Skip to content
FlowHubFluxonLab
W
General Automationfree

Standardize US Phone Numbers with Multiple Format Options and Validation

by Sunny Thaperadapted from n8n official workflow galleryUpdated Aug 2026
Share Post Share
EWWhen Executed by Another WorkflowWhen Executed b…IfCheck if first digit is valid country codeCheck if first …SeAdd valid country codeAdd valid count…SeStrip phone number formattingStrip phone num…SwCheck number of digits in phone numberCheck number of…SeFormat phone numbersFormat phone nu…SeClear invalid numberClear invalid n…12345678910
1/5
STEPS · 10
Called by another workflow

Workflow Overview: This n8n workflow template takes a US phone number as input, validates it, and returns it in multiple standard formats, including handling extensions. It's designed to streamline the process of standardizing phone number data within your automations. How it Works: Input: Accepts a phone number string as input. This number can be in various common formats (e.g., (555) 123-4567, 555.123.4567, +15551234567, 5551234567x890). Formatting Removal: Strips all non-numeric characters to isolate the core number and any potential extension. Validation: Country Code Check:** Verifies if the number starts with the US country code (+1 or 1) or assumes US if no country code is present and the length is correct. Length Check:** Ensures the main number component consists of exactly 10 digits after stripping formatting and the country code.

Tags

n8nreference-only
CategoryGeneral Automation
Triggermanual
Complexitymedium
Nodes7
AddedMay 1, 2025
W
free

Tiny tiny Rss (aka tt-rss) Feed to Mastodon

Every 10 minutes look at your published news in your Tiny tiny RSS public feed and make a toot on your mastodon. You'll need: Your mastondon URL instance Your mastondon access token Your Tiny Tiny RSS public published feed URL

by dev
free

Using the Merge Node - Merge by Key

This is an example of how you can make Merge by Key work. The “Data 1” and “Data 2” nodes simply provide mock data. You can replace them with your own data sources. Then the “Convert Data” nodes are important. They make sure that the different array items are actually different items in n8n. After that, you have then the merge with the merged data.

by mike
free

Write JSON to Disk (Binary)

The “Write Binary File” expects binary data. The JSON data is, however, JSON ;) There should really be a node that allows moving data around between both of them. For now, it can be done with a Function-Node. At least till a proper one is in place. The first node is example data, wich you can customize or replace. The second node named “Make Binary” is the important one with the custom code which makes the data binary and writes it to the correct location.

by mike