uuid validator

Faithful summary of lib/validators.ts. Validators are pure functions and run identically in the worker, the Workbench, and the MCP server.

function validUuid(value) {
  return /^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$/i
    .test(value)
    ? OK
    : fail('uuid_invalid', 'not a UUID')
}

Validators attach to a field on a custom template. The cascade runs them after mapping but before commit; failures surface in the per-row validation report.

fields:
  - column: external_id
    type: string
    validators:
      - type: uuid

• Version 6, 7, 8 UUIDs are rejected — the version nibble must be 1–5. If you emit UUIDv7, validate with a custom regex.
• Unhyphenated 32-hex form is rejected. Insert hyphens in your transform.
• NIL UUID `00000000-0000-0000-0000-000000000000` fails because the version nibble is `0`.

No template in the default catalogue ships with uuid preconfigured. Use it on a custom template via the YAML snippet above, or via the template editor.

Validators add no AI cost — they are pure functions. Every map bills a small flat per-map fee from your prepaid token wallet ($10 minimum, shared across our suite); only columns that reach the metered LLM layer, plus any-to-any convert and reshape, bill real AI tokens. See pricing →

Back to the documentation index or browse the template catalogue.