Per-node dry-run endpoint used by the workflow builder when an author clicks “Test” on a node. The supplied config is parsed against the node’s configSchema; on validation failure the response is HTTP 200 with success:false and a Zod-style issues[] array so the UI can render field-level errors (4xx is intentionally avoided because the client wrapper throws on 4xx and strips the issues payload). On success: trigger-category nodes are executed against a synthesized ExecutionContext built from input (so the response reflects the actual trigger output a workflow would see) and side-effecting nodes return a mocked output derived from outputShape (real execution is deferred until per-executor dryRun guards land). Special case: WebhookTrigger simulates the HTTP-boundary validation done by /api/webhook/workflow and surfaces the same webhookId checks the real evaluator would apply.
Documentation Index
Fetch the complete documentation index at: https://docs.tetherai.ca/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Registered node type (e.g. WebhookTrigger, SendMessage, IfCondition).
config is parsed against the node's configSchema. input is only consumed by trigger-category nodes; for non-trigger nodes it is ignored and a mocked outputShape is returned. Trigger nodes receive input flattened into an ExecutionContext (so fields like contactId, messageId, from/to/subject are read from the top level).
Test executed (success, mocked output, or validation failure). Inspect success to disambiguate.
Always 200 OK. Inspect success to disambiguate: true → trigger executed or non-trigger returned a mocked outputShape; false → config validation failed (issues array populated) OR WebhookTrigger boundary-check failed.