Validation Tools

Validate emails, URLs, phone numbers, and other data formats.

Overview

The Validation Tools connector is a workflow-side utility for checking that values match expected formats - emails, URLs, phone numbers, dates, UUIDs, and more. It runs entirely inside Spojit with no external API calls.

Use it at workflow boundaries (after a Trigger, before a downstream API call) to catch malformed data early. Cheap input validation prevents expensive downstream failures, malformed records in your database, and bounced emails on your marketing platform.

What You Can Do

The validation connector exposes these tools:

• email - Validate that a string is a well-formed email address.
• url - Validate that a string is a well-formed URL.
• phone - Validate phone numbers (international format).
• credit-card - Validate a credit card number via the Luhn algorithm.
• ip - Validate IPv4 or IPv6 addresses.
• uuid - Validate that a string is a well-formed UUID.
• iso-date - Validate ISO-8601 date or datetime strings.
• json - Validate that a string is parseable JSON.
• numeric - Validate that a string represents a number.
• alphanumeric - Validate alphanumeric-only strings (no symbols or spaces).
• hex-color - Validate a CSS hex color code.
• mac-address - Validate a MAC address.
• slug - Validate a URL slug (lowercase, hyphens, no spaces).
• is-empty - Check if a value is empty, null, or whitespace.
• password-strength - Check the strength of a password against common rules.

Authentication and Setup

No connection or authentication is required. These tools are built into the platform and available in every workflow by default - just drop a Connector node onto the canvas and pick the tool you need.

Using in a Workflow

Add a Connector node, select Validation Tools, and choose Direct Mode with the validator you need. Each tool returns a boolean and a short reason - pipe the result into a Condition node to branch valid records to the main path and invalid records to a logging or alert path.

Tips

• Validate after Transform, not before - a Transform that lowercases and trims often turns an invalid input into a valid one.
• Bundle validators for common record shapes (e.g. validate email, phone, and required-field is-empty in parallel) and short-circuit on the first failure.
• Log the input value and validator result for invalid records so you can spot patterns (typos, malformed exports, regional formats).

Common Pitfalls

• Phone number formats - The validator expects international E.164 format. Strip spaces, parentheses, and dashes first.
• Email validation lies - The validator checks format only, not deliverability. An invalid mailbox at a valid domain still passes.
• Strict ISO dates - 2026-01-01 passes; 01/01/2026 fails. Normalize dates with the Date connector before validating.
• URL slugs that contain uppercase - The validator rejects them. Run text/slugify first if your input is title-cased.

Common Use Cases

• Build an AI-Powered Data Validation Pipeline
• Validate and Clean CSV Data Before Import
• Use AI to Clean and Normalize Messy Data

Related Articles

• Adding a New Connection
• Regex Tools
• CSV Tools
• JSON Tools

For technical API details and field specifications, see the Validation Tools documentation.