Technical Specification·3-Tier Policy & Architecture

How Blacksmith Works

An autonomous reliability layer for n8n and Make. When schemas fracture, Blacksmith catches the payload, evaluates deterministic 3-tier safety rules, and quarantines ambiguous financial drift to prevent silent ledger corruption.

The Two Operating Modes

Honest architectural boundaries: n8n and Make do not natively support stateful mid-node resumption without pre-configured wait loops.

Mode A: Synchronous Inline Proxy

Zero Workflow Changes · Synchronous Edge Validation

Zero Downtime

01. INGRESS

Point Sender to Ingress URL

Update the webhook URL in Stripe, HubSpot, or Typeform to your Blacksmith ingress endpoint (/v1/in/:token). No custom headers required.

02. EVALUATION

3-Tier Deterministic Repair

Tier 1 & Tier 2 transformations (syntax, numeric string cast, casing aliasing) are auto-applied in ~140ms. Tier 3 financial drifts are halted.

03. FORWARDING

SSRF-Protected Forwarding

The pristine payload is forwarded to your real n8n webhook URL with telemetry headers (X-Blacksmith-Repaired). Fail-open on timeout protects pipeline uptime.

3-Tier Policy Simulator· Measured Rules

Witness how Blacksmith differentiates safe auto-repair from financial ContractBreaker halts.

Tier 1 & 2: Parsed numeric string '8950' to integer 8950, and normalized casing 'customerId' → 'customer_id'. Clean payload returned.

Tier 1 & Tier 2 (Safe Auto-Apply)

Damaged Input Payload

{
  "event": "charge.captured",
  "customerId": "cus_J91bX9",
  "amount": "8950",
  "currency": "usd",
  "receipt_email": "ceo@acme-corp.com"
}

Clean Repaired Output

{
  "event": "charge.captured",
  "customer_id": "cus_J91bX9",
  "amount": 8950,
  "currency": "usd",
  "receipt_email": "ceo@acme-corp.com"
}

Canonical Ingress Endpoint

https://www.useblacksmith.app/v1/in/demo_inlet_token_safe

Open Dashboard