HubPay Trigger
AI-generatedSummary
Receive and process HubPay webhook events filtered by selected types, verifying signature unless allowed unsigned, and output enriched event data to trigger workflows.
Inputs
- Events (required) — Select which HubPay event types (e.g., charge.paid, charge.failed) should trigger the workflow. Only checked events will pass through; other events are acknowledged with 200 OK without firing the workflow.
- Allow Unsigned Webhooks — Boolean flag to skip validating the X-Hubpay-Signature HMAC header. Should only be enabled for local testing; must be disabled in production to enforce webhook security.
Output shape
a single JSON object containing the webhook event payload enriched with metadata fields (_meta) such as event_id, event_type, and received_at timestamp.
The trigger acknowledges non-selected event types with HTTP 200 but does not output data to the workflow. If signature verification fails, the webhook response is HTTP 401 and no workflow execution occurs. Invalid JSON bodies receive HTTP 400 and no execution. The output data includes the original webhook payload plus additional metadata under _meta.
Examples
Example 1: Trigger workflow only on 'charge.paid' and 'charge.refunded' events with signature enforcement
Set 'Events' to ['charge.paid','charge.refunded'] and 'Allow Unsigned Webhooks' to false. Provide HubPay API credentials with a webhook secret configured to validate incoming webhook signatures.
Example 2: Test webhook reception locally without signature validation
Enable 'Allow Unsigned Webhooks' to true to bypass signature checks, useful when invoking webhook manually via tools like curl during development.