Why do you want to contribute?
I would like to add Xquik as a first-class source for the new hosted-webhooks provider catalog. Xquik sends signed X monitor events with an eventType body field, deliveryId idempotency key, millisecond timestamp, nonce, and sha256= HMAC signature. Trigger.dev's existing data-only verifier can express that contract without new engine code.
I will keep this to one provider contribution: the core provider config, registry metadata, representative public-doc payload samples, generated aggregates, and the existing sign-then-verify round-trip suite. It will add no dependency or unrelated change.
Prior contributions or relevant experience
I maintain the webhook implementation and public API contract in Xquik. The public Xquik webhook documentation specifies the payload, replay protection, signature headers, and signing string this contribution will model.
Why do you want to contribute?
I would like to add Xquik as a first-class source for the new hosted-webhooks provider catalog. Xquik sends signed X monitor events with an
eventTypebody field,deliveryIdidempotency key, millisecond timestamp, nonce, andsha256=HMAC signature. Trigger.dev's existing data-only verifier can express that contract without new engine code.I will keep this to one provider contribution: the core provider config, registry metadata, representative public-doc payload samples, generated aggregates, and the existing sign-then-verify round-trip suite. It will add no dependency or unrelated change.
Prior contributions or relevant experience
I maintain the webhook implementation and public API contract in Xquik. The public Xquik webhook documentation specifies the payload, replay protection, signature headers, and signing string this contribution will model.