Templates / Verify a phone number with uProc

Verify a phone number with uProc

Needs changes

by Miquel Colomer ✓ · 1,613 views · created 2020-12-30 · Lead Generation

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: Function Item (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.

What this workflow does

This workflow has 4 nodes and runs manually, when you click “Execute workflow”. Along the way it connects uProc.

How it runs

Trigger: Manually, when you click “Execute workflow”.

  1. Create Phone Item (Function Item): runs custom JavaScript per item (legacy Function Item node)
  2. Parse and Validate Phone (uProc): uses uProc
  3. Phone is Valid? (If): checks a condition and branches into true / false

Services it uses

uProc

Before you upgrade to n8n 3.0

1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:

  • Function Item (legacy) in Create Phone Item: replace with Code node, mode 'Run Once for Each Item'.

Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).

Removed in 3.0Replace with
Function Item (legacy)
Create Phone Item
Code node, mode 'Run Once for Each Item'

Nodes used (4)

From the author

Do you want to avoid communication problems when launching phone calls? This workflow verifies landline and mobile phone numbers using the uProc Get Parsed and validated phone tool with worldwide coverage. You need to add your credentials (Email and API Key -…

Excerpt from Miquel Colomer's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.