Loading page
Developers
Start workflows from your own systems, receive execution events and inspect results with APIs and webhooks designed around how workflows actually run.
curl -X POST https://api.example.com/v1/workflows/wf_lead_qualification/executions \
-H "Authorization: Bearer $ZYNAPTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "input": { "lead": { "company": "Sample Robotics" } } }'Illustrative examples
api.example.com) and can't be executed yet.Developer platform
Trigger executions, read results and manage workflows over REST.
Read moreStart workflows from inbound requests and subscribe to execution events.
Read moreScoped API keys per workspace, with rotation and separate test keys.
Read moreConnectors plus generic REST and webhook steps for any other system.
Read moreA defined lifecycle from queued to succeeded, with retries and wait states.
Read moreA sandbox workspace, request logs and test events. CLI and SDKs are planned.
Read moreWorkflow execution
Each execution moves through explicit statuses. Approvals put it in a waiting state, transient failures are retried, and a failed step can be retried without restarting the run.
failed retry step running
{
"type": "execution.failed",
"execution": "exec_0be6f4a3",
"step": "post_to_accounting",
"error": { "code": "upstream_unavailable" }
}Developer tooling
Status is stated for each item. None of it is available yet.