Zapier, Make and REST hooks

wrkflow has the endpoints an automation platform needs to trigger on its events: subscribe and unsubscribe (REST hooks), polling lists and sample payloads. There is no published Zapier or Make app yet, so you build a private one in their developer tools with the steps below. It's a Team-plan feature.

Create a key

1. 1In Settings → API and webhooks, choose Create API key.
2. 2Give it Read responses, Read surveys and Manage event subscriptions (hooks:write).
3. 3Copy the key (wrk_…) into the platform's connection. Use GET /api/v1/me as the connection test.

Instant triggers

The platform subscribes with POST /api/v1/hooks and an event (response.created or survey.published), the URL it wants deliveries at, and optionally a survey_id. wrkflow answers with an id, which the platform sends back as DELETE /api/v1/hooks/{id} when the automation is turned off.

curl https://your-site/api/v1/hooks \
  -H "Authorization: Bearer wrk_…" \
  -H "Content-Type: application/json" \
  -d '{"event":"response.created","target_url":"https://hooks.zapier.com/hooks/standard/123/abc/"}'

Deliveries are the same signed webhooks you can add by hand, so they show up in Settings → API and webhooks with their delivery log, and are retried the same way for about a day. Pausing or deleting one there, or revoking the key, stops it. When the platform answers a delivery with 410 Gone (Zapier does when a Zap is deleted), wrkflow removes the subscription.

Polling and samples

GET /api/v1/triggers/response.created and GET /api/v1/triggers/survey.published return the newest items first, each with a unique id and the same fields a delivery carries. GET /api/v1/hooks/samples returns made-up examples for the platform's editor.