Fire test or replay an automation run
POST body is a 3-branch union, dispatched by body shape:
- Fire —
{ triggerEventId, payload, idempotencyKey? }. Starts one Vercel Workflow per published automation attached to the trigger and returns theFIRE_EVENT_RESPONSEenvelope{ success, status: "triggered" | "idempotent_replay", code, message, receivedAt, details: { automationRunIds[], triggerInstanceId, counts, … } }. Readdetails.automationRunIds. - Test —
{ automationId, mode: "test", payload? }. Suppression-aware test run; no real mail sent. Returns the flat{ automationRunIds[], status: "test_started", … }shape (top-levelautomationRunIds). - Replay —
{ automationRunId, mode: "replay" }. Re-runs a prior run with the same payload + mode against the automation’s current saved draft. ReturnsEXECUTIONS_POST_RESPONSEwithstatus: "replay_started"+ the newautomationRunIds.
Supports Idempotency-Key header on the fire branch — retries with the same key return the original automationRunIds without starting duplicate workflow runs.
Authorizations
Send your Brew API key as Authorization: Bearer brew_xxx.
Headers
Optional idempotency key for safe retries. Reusing the same key with the same request body returns the original response for 24 hours.
1 - 100Body
Response
Idempotent replay — original automationRunIds returned.
- Option 1
- Option 2
Discriminator for the response category. Pairs with code. A trigger with no published automation attached returns status: "failed" + code: "NO_PUBLISHED_AUTOMATION" (HTTP 422). Successful fires always return status: "triggered".
triggered, idempotent_replay, ready, invalid_api_key, invalid_json, failed, forbidden, payload_mismatch, trigger_event_not_found ISO-8601 timestamp the request was processed at.