Zapier setup

This uses Zapier Manager triggers and a Webhooks by Zapier → POST action to send problems to FlowSentinel. Publishing multi-step Zaps may require a Pro plan.

Headers (add both)

Name: Content-Type • Value: application/json
Name: X-FlowSentinel-Secret • Value: your Vercel ZAPIER_INCOMING_SECRET

Zap 1 — New Zap Error → POST

Trigger: Zapier Manager → New Zap Error
Action: Webhooks by Zapier → POST
URL: https://flowsentinel.app/api/zapier/incoming • Payload Type: json
Data (add rows):

event          = zap_error           (typed)
zap_title      = Title               (from trigger)
error_message  = Message             (from trigger)
zap_id         = Root Id OR Node Id OR Task History Link (pick one stable id)
error_time     = Occurred / Created / Date (if none available, omit)

Zap 2 — Zap Turned Off → POST

Trigger: Zapier Manager → Zap Turned Off
Action: Webhooks by Zapier → POST
URL: https://flowsentinel.app/api/zapier/incoming • Payload Type: json
Data (add rows):

event          = zap_turned_off      (typed)
zap_title      = Title               (from trigger)
zap_id         = Root Id OR Node Id OR Task History Link
error_message  = Zap turned off      (optional)
error_time     = Occurred / Created / Date (if none, omit)

Test & verify

Use the Trigger’s sample and “Test action” to send a POST.
Open /api/errors/recent — you should see the entry. (Turned-off events are stored as warnings and will appear in “Recent issues”.)