Pingen Trigger
AI-generatedSummary
Subscribes to one Pingen event category and starts the workflow when Pingen sends a matching webhook. On activation, registers the webhook for the selected organisation and environment; on deactivation, removes it.
Inputs
- Environment — Select Production or Staging. Each uses its matching Pingen credential; Staging is a free test environment.
- Organisation Name or ID (required) — Choose the Pingen organisation where the webhook is registered, or provide its ID with an expression.
- Event Type — Choose Issues, Sent, Delivered (default), or Undeliverable. Add another trigger node to subscribe to another event type.
- Webhook Secret (required) — Signing secret, up to 32 characters, registered with the webhook and used to verify incoming HMAC-SHA256 signatures.
Output shape
One workflow item per accepted webhook, containing a JSON object with eventType, id, type, flattened data attributes, relationship IDs where present, and included resources when provided.
The trigger accepts POST requests with the Pingen JSON:API content type and a valid signature. Invalid signatures, content types, empty or invalid JSON, and missing data envelopes receive HTTP error responses instead of workflow data.