Private Beta · 5 Design Partner Spots Available
Free for B2B Automation Agencies

Catch broken n8n & Make webhooksbefore your clients notice.

When a client edits a HubSpot custom property, a form builder changes field names, or an LLM node outputs markdown fences, production workflows crash without warning. Blacksmith acts as your autonomous safety proxy—normalizing drifted schemas deterministically, quarantining financial mismatches, and resuming executions with zero downtime.

Enter Dashboard
No signup or credit card required for sandbox test
·ContractBreaker Ledger Protection·Fail-Open Ingress Safety
Golden Eval Benchmark

105 / 105

✓ 100% Passed Test Cases
Wrong-Repair Rate (Financial)

0.0%

🛡 Measured on Eval Set
Fail-Open Uptime Guard

<1500ms

⚡ Timeout Pass-Through
Data Retention Policy

72 Hours

🔒 Ephemeral Vault TTL
Interactive Live SandboxREAL 3-TIER ENGINE
Select failure pattern:
Damaged Payload (n8n)Simulated Example
{
  "event": "charge.captured",
  "customerId": "cus_8891Xa",
  "amount": "4900",
  "currency": "usd",
  "receipt_email": "ceo@acme-corp.com"
}
Healed Contract Outputtier_2_alias
{
  "event": "charge.captured",
  "customer_id": "cus_8891Xa",
  "amount": 4900,
  "currency": "usd",
  "receipt_email": "ceo@acme-corp.com"
}
Tier 1 & Tier 2 Auto-Applied: Normalized key casing 'customerId' → 'customer_id' and parsed numeric string '4900' to integer 4900.
The Reality of Automation Maintenance

Why Automations Fail at 3:00 AM

Third-party APIs don't break because developers write bad code. They break because real organizations evolve dynamically:

INCIDENT PATTERN 1

CRM Custom Field Renames

A sales operations team edits a HubSpot or Salesforce property label. Downstream n8n nodes expecting deal_amount crash because the payload now emits deal_total_revenue.

INCIDENT PATTERN 2

LLM Output Formatting Drift

An upstream OpenAI or Gemini node adds markdown code fences (```json) or outputs camelCase instead of snake_case. Make's JSON parser throws an unhandled exception.

INCIDENT PATTERN 3

Type & Currency String Fractures

A checkout system formats a number as a localized string ("4900"). Strict destination databases (PostgreSQL, Supabase) reject the row insert with a cast failure.

Transparent Beta Access

100% Free During Closed Beta

We are working closely with 10 automation agencies to perfect deterministic repair rules before commercial billing. No credit card required.

Design Partner License

Phase 2 Closed Beta
$0
  • Unlimited webhook ingress during beta
  • 3-Tier deterministic repair & ContractBreaker
  • Dead-Letter Vault with 72-hour TTL
  • Direct 1-1 founder engineering channel
Clarity & Boundaries

Frequently Asked Questions & Limitations

What is auto-repaired vs. quarantined?

Tier 1 (syntax, numeric string cast) and Tier 2 (exact casing aliasing) are auto-applied deterministically. Tier 3 (any mutation touching financial terms like subtotal vs total, currency codes, or identity tokens) is strictly quarantined to prevent silent ledger corruption.

Does Blacksmith send customer values to AI models?

No. In default Schema-Only mode, Blacksmith strips all values and sends only structural JSON keys and types to Gemini. The LLM only proposes a mapping; code evaluates the mapping locally.

What happens if Blacksmith experiences high latency?

Blacksmith enforces a strict 1500ms Fail-Open timeout. If the repair engine exceeds the budget, the raw payload is forwarded untouched to prevent upstream timeouts, logging a forensic event in the vault.

What is NOT supported? (System Limitations)

  • Binary file payloads (PDFs, images) are not reparable; only JSON webhooks are supported.
  • Signed webhooks (Stripe/Shopify HMAC) cannot be mutated inline without breaking upstream signature verification; they must use Drift-Alert mode or be verified at proxy ingress.
  • Paylod bodies exceeding 256 KB are rejected to maintain sub-second throughput.