Skip to main content
Triggers & Integrations

One HTTPS POST to connect your website or App to AI workflows

No wiring up model SDKs, retries, or queuing yourself—your system sends a JSON, the fields map to workflow variables automatically, and once the AI is done it sends the result back to wherever you specify.

Start for FreeRead the Webhook docs →
API Key or HMAC-SHA256Automatic JSON field mapping14 v1 API endpoints
POST /api/webhooks/{id}/triggerJSON · ≤ 1MB
# One POST from your system triggers the workflow
curl -X POST https://your-host/api/webhooks/{id}/trigger \
  -H "X-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "user_feedback": "PDF export keeps failing after upgrading",
    "user_id": "u_84021",
    "app_version": "3.2.1"
  }'

# Top-level fields map automatically to workflow variables of the same name
# Then: AI classifies → drafts a reply → sends after human confirmation
Trigger mode

Four ways to start a workflow

Clicking to run manually works too; the four below let workflows run automatically alongside your systems and schedule.

CRONScheduled TriggerFive-field cron expressions with time zone settings, plus fixed intervals and one-time schedules; in multi-instance deployments, a distributed lock guarantees a trigger fires only once at any given moment.
0 8 * * *Distributed lock
HOOKWebhook TriggerYour system can trigger the workflow by sending a POST request with a JSON body. API Key authentication is primary; HMAC-SHA256 signatures remain supported for compatibility. The request body is limited to 1 MB.
X-API-Key≤ 1MB
APIREST APIThe v1 API has 14 endpoints: trigger executions, check results, download artifacts, and even respond to approvals from your own system. API Keys grant least privilege across 6 permission scopes.
14 endpoints6 permission scopes
CHAINChained SchedulingThe DELAYED_COMPLETION trigger: after workflow A completes, wait N seconds, then trigger workflow B automatically; maxRuns sets an upper bound to keep the chain from running away.
A → BmaxRuns
Outbound delivery

Results delivered where your team already works

When a workflow finishes, reports, alerts, and approval requests go to IM and email, or become file attachments.

IM7 IM ChannelsSlack, Discord, Telegram, WhatsApp, WeCom, DingTalk, and Lark; of these, Telegram supports two-way messaging.
MAILEmail DeliveryBoth execution reports and approval notifications can go by email, and you can handle approvals right from the inbox.
FILEFile DeliveryReports can be output as .md, .xlsx, .pdf, or .csv files and sent as attachments with a message or email.
MCP

For systems with no ready-made integration, connect an MCP Server to the Agent

An Agent in your workflow can attach any MCP Server as a tool and call it on its own during execution.

  • Attach an MCP Server in an agent_based step, and the Agent calls it as a tool during execution
  • Wrap an internal system in an MCP Server and Agents in your workflow can use it
  • Complements sandboxed code steps: write code for deterministic calls, and leave open-ended tasks to an Agent with tools
Integration examples

What it looks like once connected

Two common patterns: both start with a single POST from your system, leaving key actions for human confirmation.

Website form, wired to lead analysis
  • A visitor submits the Contact Us form, and your backend POSTs the fields to the Webhook
  • The AI reads the company name, message, and referring page to gauge lead intent
  • High-intent leads stop at an approval step, a notification goes to Slack or email, and sales follows up after confirming
webhookManual Approval
In-app user feedback, wired to classification and replies
  • A user submits feedback in the App, and the server forwards a POST
  • A classifier step sorts feedback into bug, feature request, and billing issue
  • The AI drafts a reply, sent to the user only after human confirmation
webhookManual Approval
Capability boundaries

There's no catalog of hundreds of SaaS connectors here

Braidrun doesn't offer a drag-and-drop catalog of HTTP connectors. Calls to external systems go in code steps (7 languages, running in a Docker sandbox) or come in as MCP tools attached to an Agent.

Put another way: any system reachable over HTTP or an official SDK can go into a workflow—the cost is a few lines of code.

Webhook Trigger DocsA full rundown of authentication methods, variableMapping field mapping, request examples, and the 1MB limit.Open the docs →v1 API ReferenceRequest and response formats for the 14 endpoints, plus a reference for the 6 API Key permission scopes.Open the docs →
Connect your system to your first workflow
Start on the Free plan and get a process working from a template; when you need scheduled and Webhook triggers, upgrade to Pro to enable them.
Start for FreeRead the Webhook docs