Developer automation
Bring governed AI agent workflowsinto the systems you already run
Trigger with APIs and webhooks, call external services and inspect every execution without rebuilding the orchestration layer.
Done in 13m36s · usage and cost on the record
One flow from orchestration to delivery
The caller receives an execution ID and can inspect the result. The v1 API uses scoped API keys. Webhook payloads map into workflow variables and return an execution identifier.
Browse all services- 01Internal webhookREST · JSON
- 02Call external APIEVENT
- 03AI processes dataOBSERVE
- 04Conditional branchCONTROL
Core capabilities
See how the workflow becomes operational
The v1 API uses scoped API keys. Webhook payloads map into workflow variables and return an execution identifier.
Product proof
- 01POST /api/webhooks/{id}/trigger
- 02X-API-Key authentication
- 03GET /api/v1/executions/{id}/result
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.
POST /api/webhooks/{id}/triggerX-API-Key authenticationGET /api/v1/executions/{id}/resultCore capabilities
Concrete primitives for integration
REST API
Trigger executions, inspect status, retrieve results and respond to approvals through scoped endpoints.
Webhook triggers
Send a JSON payload to a workflow-specific endpoint protected by an API key.
Logs and recovery
Inspect step output, errors and execution history; retry behavior is controlled by workflow configuration.
Credentials and deployment
Use managed credential references and deployment options documented for your environment.
Verified product scenario
Designed for real operating work
Production integrations need authentication, retries, state and evidence.
REST API
Trigger executions, inspect status, retrieve results and respond to approvals through scoped endpoints.
REST · JSONWebhook triggers
Send a JSON payload to a workflow-specific endpoint protected by an API key.
EVENTLogs and recovery
Inspect step output, errors and execution history; retry behavior is controlled by workflow configuration.
OBSERVEHow 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
The operational gap
Move from manual gaps to an accountable flow
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: every team maintains its own trigger, retry and logging glue.
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.
Start on the free tier
Free includes 5 workflows and unlimited AI assistant use (model costs use your credentials); upgrade to Pro for schedules, webhooks, and all 8 step types.
- 40 regular model requests per day
- AI Assistant
- 5 workflows
- 3 basic step types
- No credit card required
- Unlimited regular model requests
- Access to advanced models
- 50 workflows
- All 8 step types
- AI assistant + debugger
- Unlimited regular model requests
- Access to advanced models
- 200 workflows
- Includes 1 team seat
- Team management and collaboration
- Additional seats $9.9/seat/month
- Unlimited regular model requests
- Access to advanced models
- Unlimited workflows and steps
- Includes 1 team seat
- Team management and collaboration
- Additional seats $19.9/seat/month
- Audit logs and compliance
- SSO / SAML
FAQ
Questions, answered
Developer automation
Trigger the first workflow from your system
Use the documented webhook contract, then inspect the execution and result.




