Store a webhook header’s secret value
Encrypts the value and answers its id, which a webhook step’s header holds as `secretId` (D198); the value is never answered again.
Encrypts the value and answers its id, which a webhook step’s header holds as secretId (D198); the value is never answered again.
apiKey writeAuthorizationBearer <token>A workspace API key (pf_…), created under Developers → API keys.
Scope: write
id*string^(auto)_[0-9A-Za-z]{8}$idempotency-key?stringRun this write once: a retry with the same key gets the first answer (24 hours).
1 <= length <= 255application/json- body
value*string1 <= length <= 2000Created
application/json- response
id*stringuuidcurl -X POST 'https://api.postforge.dev/v1/automations/string/webhook-secrets' \ -H 'Content-Type: application/json' \ -d '{ "value": "string"}'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"}Every time an automation was triggered, and what came of it GET
Every time its trigger fired for someone, newest first (D206): entered, with their run as it is now (in it, at which step and until when; completed; left early; failed), or why not (the trigger’s conditions, who can enter, entered before, still in it, nobody known). `q` finds people by email or name; `status` and `step` filter on the run.
Preview a webhook step’s request POST
The request a webhook step would send, secret header values hidden, with the values it’s filled in with: for a profile and an event (`eventId`); without them, the person and event of the trigger’s latest event (a profile’s own latest when only the profile is given). With `send: true` it’s sent too, signed, and the answer’s status and start come back. Nothing is logged on a run.