Skip to main content
Conduit
Sign up
Operational intelligence for the AI-native enterprise

Workflow automation
that doesn't hide
how it works.

Open data model. Round-trip JSON. Layered auth visible end-to-end. Audit on by default. Built around the only noun that connects everything — the workflow.

Sign up · betaSign in
Free during beta No credit card Export anything

stripe-webhook.conduit.json

{
  "schema": "conduit.workflow.v1",
  "workflow": {
    "title": "stripe-webhook",
    "steps": [
      { "category": "trigger", "kind": "webhook" },
      { "category": "routing", "kind": "if",
        "condition": { field: "type", is: "charge.succeeded" },
        "branches": {
          "then": [
            { "category": "export", "kind": "slack" }
          ],
          "else": [
            { "category": "routing", "kind": "sleep", "config": { "seconds": 5 } }
          ]
        }
      }
    ]
  }
}█
⏰

Step 1 · Trigger · webhook

stripe webhook

🔀

Step 2 · Routing · if

when type is charge.succeeded

[✓ TRUE BRANCH]

🗄

Step 2.1 · Export · slack

post to #payments

[✗ ELSE BRANCH]

🔀

Step 2.2 · Routing · sleep

wait 5s

+Webhook· POST /stripe/webhookstripe webhook
−If· type is "charge.succeeded"branch on event
[ ✓ THEN ]
+Slack· post to #paymentsalert ops
[ ✗ ELSE ]
+Sleep· 5sback off

/ to add a block — try /if, /loop, /switch, /try, /parallel

[ ⌘⌥↑↓ move · ⌘⌥→ indent · ⌘⌥← outdent · / menu · ⌘⏎ run from here ]

same json · YAML / JSON

auto · click to jump

55

Step kinds

11

Export formats

9

Import formats

100%

Round-trip JSON

§ 01principles

A workflow runtime built for ops, not magic.

Conduit is a workflow runtime + control plane. Steps run on real executors — HTTP with SSRF guards, LLM calls with structured-output schemas, chat webhooks, transforms, secrets-aware everything. No black boxes. No opaque cloud connectors.

Workflows are the noun

One graph connects every secret, connection, run, step, and audit row. Search across step config, not just titles.

Audit on by default

Every credential read, every step run, every secret rotation. Exportable as JSON / NDJSON / CSV / CEF / SIEM.

Open data model

Conduit JSON round-trips clean across accounts and environments. Your workflow is a file, not a vendor lock.

§ 02executors

Real or simulated. No fake checkmarks.

Real executors hit the network for real. Simulated nodes pass through the run engine so you can wire workflows end-to-end while we ship the real backend. Roadmap turns simulated into real one node at a time. We tell you which is which.

REAL

Hits the actual API

  • HTTP

    SSRF-guarded · Connection auth: api-key / OAuth2 / Basic / mTLS

  • LLM chat

    OpenAI · Anthropic · Groq

  • OpenAI structured AI

    Embeddings · classifier · structured-output (json_schema) · function-call

  • Chat webhooks

    Slack · Discord · Microsoft Teams

  • Data plumbing

    JSON parse · CSV parse · prompt template · token counter

  • Routing

    Sleep / wait (up to 3600s)

  • Transforms

    Map · Cast · Dedupe · Formula · Filter (CCL conditional AST)

SIM

Returns plausible fake output

  • Postgres / MongoDB / S3 / Sheets / Airtable / Notion / Salesforce / Zendesk
  • Twilio SMS · Twitter / X post
  • PDF / CSV / JSON file parsers
  • Loop · switch · parallel · try (control flow scaffolded; execution Phase 1f)

# each row graduates to REAL on its own dedicated PR.

§ 03interop

No vendor lock. Round-trip in / out.

Native Conduit JSON exports + imports cleanly across accounts and environments. Third-party exporters land best-effort skeletons for migration; refine after import.

EXPORT

11 formats

  • Conduit (native)
  • n8n
  • Zapier
  • Make
  • Activepieces
  • Pipedream
  • Postman
  • HAR
  • Airflow · py
  • Temporal · ts
  • GitHub Actions

IMPORT

9 formats

  • Conduit (native)
  • n8n
  • Zapier
  • Make
  • Activepieces
  • Postman
  • HAR
  • curl
  • OpenAPI 3.x

# OpenAPI imports register as a reusable library — every operation becomes a pickable step kind.

§ 04auth

Connections layer. Secrets resolve. The UI tells you which.

Connections are reusable auth configs. Secrets are encrypted values referenced by name. The status banner on every HTTP step tells you when they layer, when they replace, and when they don't apply — before you commit.

Connections

api-key · OAuth2 · Basic · mTLS · Postgres.

  • ›Replaces vs layers vs transport-only status banner
  • ›Reusable across every workflow
  • ›Per-connection usage drill-down

Secrets vault

Values never returned by the API.

  • ›Per-secret usage badge
  • ›Rotation history + 90-day rotation-due warning
  • ›{{secret.name}} interpolation at run time

Account security

2FA TOTP · backup codes · email verification.

  • ›Session list with revoke
  • ›Magic-link login
  • ›In-session change password

# HashiCorp Vault backend for bridge-side secrets — roadmap Phase 13. SSO / SAML / SCIM for enterprise pilots — roadmap Phase 8d.

§ 05bridges

Run workflows where the network already lives.

Enroll a bridge once; it heartbeats home; workflows route to the right node. Fleet metrics in the dashboard. On-prem networks, local devices, isolated VPCs — all reachable without inbound holes.

Fleet visibility

Search + filter by name / platform / state. Per-bridge heartbeat. Offline-threshold alerts.

Audit forwarded

Every credential read + step exec on the bridge fires an audit event back to the central log.

Vault backend

HashiCorp Vault adapter on the roadmap (Phase 13) for bridge-side secret resolution + mTLS.

§ 06wedge

The workflow is the central noun.

Every other category — secrets, connections, bridges, agents, runs, audits — has natural edges to a workflow. Most ops platforms anchor on configuration items, agents, services, or permissions. Conduit anchors on the workflow because the workflow is what actually moves data, fires APIs, and touches credentials.

What this unlocks

  • “What uses this secret?” answered from real runtime telemetry, not periodic scans.
  • Blast-radius preview before secret rotation.
  • Cross-workflow drill-through from audit logs.
  • Workflow as the unit of operational intelligence — not configuration items.

# Tracked in the public roadmap as Phase 6.

From the brainstorm research

“ServiceNow’s noun is configuration item. Microsoft’s is agent. Port’s is service. Veza’s is permission. Conduit’s must be workflow — because workflows are the only noun that naturally has edges to all other objects.”

— Operational intelligence positioning, ch. 4

§ 07built for

Built for the people who get paged at 3am.

Four customer archetypes drive every shipped feature. Their pain points become acceptance criteria. Their journeys become MVP scope.

01 · Chief AI Officer

F500 · AI-native product co

Rosalind

CAO

“We shipped 47 agents last quarter. I can't tell the board what they have access to.”

Success metric: Show me every agent and every credential it touches.

02 · Chief Information Security Officer

5K–50K employee enterprise

Marcus

CISO

“We have 14,000+ non-human identities and no way to audit which have PII access.”

Success metric: Audit trail of every credential use.

03 · VP Platform Engineering

Mid-size tech · 50–300 eng

Jamie

VP Platform

“Workflow goes rogue, I get a PagerDuty alert at 3am. Half my on-call time is investigative archaeology.”

Success metric: 30-minute incident resolution.

04 · Security Analyst / Engineer

3–5 person sec team

Alex

Sec Analyst

“External auditor asks 'what has access to customer data?' I don't have a fast answer.”

Success metric: Ad-hoc queries that answer 'who/what touches X' in minutes, not hours.

# Source: PRD v4 § 02 — Personas & Representative Journeys.

Meet the personas

Wire your first workflow.

Beta. Free to use today. Pricing announced before the beta tag comes off.

Sign up · betaSign in

theme

?theme=clean — shareable