Skip to content
New: a free website for your business, live in 48 to 72 hoursWorkflow automation on n8n and Claude, built for your businessFixed price, agreed before we start · Live in 5 to 10 business days30-day money-back guarantee on every planProfessional firms · Agencies · E-commerceYou own every workflow, in your own n8nClaude API: your data is not used for trainingHuman approval on every sensitive stepFree automation audit, no obligation
PURIST
30 days
Money-back window
14 h/wk
Modeled time saved
99.97%
Uptime SLA
< 7 days
Deploy time
PURIST AI
Claude Opus 4.7 · n8n v1.71 · <80ms
What type of business are you running? I'll show you exactly which processes we'd automate first and your estimated ROI.
Powered by n8n + Claude Opus 4.7 Get my free automation plan →
Data
Intermediate

Normalisation (data)

Reformatting incoming data into a consistent standard. Example: phone numbers arrive as "+44 7700 900123", "07700900123", and "0044-7700-900123" from different forms normalisation converts all three to E.164 format before storing.

Expert insight

Normalising data (converting "NY", "New York", and "N.Y." to one consistent value) before it enters a workflow's decision logic prevents a whole class of bugs where a conditional check fails simply because the incoming value doesn't exactly match what the condition expected, not because the underlying business logic was wrong.

In a real workflow

Country names like "UK", "United Kingdom" and "GB" are normalised to the ISO code "GB".

Common mistakes

  • Normalising differently in each workflow.
  • Losing the original value.

Complexity level

Intermediate

Requires some familiarity with automation concepts.

Quick facts

Category Data
Level
Intermediate

Browse the full glossary

← All 325 terms

See it in action

Want Normalisation (data) built into your automation?

Book a free audit and we'll show you exactly how this applies to your business.

Get my free automation plan →