Developer automation

Bring governed AI workflows into the systems you already run.

Q: Is a REST API available?

Yes. The v1 API exposes scoped endpoints for execution, results, artifacts and approvals.

Q: Can a webhook run a workflow?

Yes. A workflow webhook accepts JSON and returns an execution ID.

Q: Can we connect our own AI model?

Models available to workflows are determined by the provider and model configuration in your environment.

Q: How are API keys and credentials protected?

API keys use explicit scopes. Workflow credentials are referenced through the credential system rather than embedded in page content or workflow output.

Q: Can we self-host or use a private environment?

Deployment capabilities depend on your edition and infrastructure agreement. Contact the team to validate your required topology.

Trigger with APIs and webhooks, call external services and inspect every execution without rebuilding the orchestration layer.

Try developer features Read the API docs

No credit card required

Product proof

A real request, a real execution record

The v1 API uses scoped API keys. Webhook payloads map into workflow variables and return an execution identifier.

01POST /api/webhooks/{id}/trigger

02X-API-Key authentication

03GET /api/v1/executions/{id}/result

Core capabilities

Concrete primitives for integration

REST · JSON

REST API

Trigger executions, inspect status, retrieve results and respond to approvals through scoped endpoints.

EVENT

Webhook triggers

Send a JSON payload to a workflow-specific endpoint protected by an API key.

OBSERVE

Logs and recovery

Inspect step output, errors and execution history; retry behavior is controlled by workflow configuration.

CONTROL

Credentials and deployment

Use managed credential references and deployment options documented for your environment.

How it runs

An internal event becomes a governed execution

The caller receives an execution ID and can inspect the result.

01Internal webhook
02Call external API
03AI processes data
04Conditional branch
05Return or publish result

Reference integration

Webhook-triggered internal triage

An internal system posts a JSON event. The workflow enriches it through an API, uses AI to classify it, branches by outcome and exposes the recorded result.

BEFORE

Before: every team maintains its own trigger, retry and logging glue.

WITH BRAIDRUN

After: orchestration is centralized while the internal system keeps its contract.

The operational gap

Orchestration is more than a model call

Production integrations need authentication, retries, state and evidence.

Glue code expands

Triggers, queues, retries and result polling become another platform to maintain.

Failures are opaque

A single response does not explain which step failed or what input it received.

Security gets fragmented

Keys and permissions spread across scripts without a consistent access boundary.

FAQ

Questions, answered

Is a REST API available?

Can a webhook run a workflow?

Can we connect our own AI model?

How are API keys and credentials protected?

Can we self-host or use a private environment?

Developer automation

Trigger the first workflow from your system

Use the documented webhook contract, then inspect the execution and result.

Start freeNo credit card required