Trigger 2. Monitor event REST hook
Use REST Hooks for near-real-time X (Twitter) tweets, replies, quotes, and retweets.Choose a secure webhook path
Use a verification relay. Keep the one-time signing secret outside Zapier logs.Production relay
Let the relay create the Xquik webhook. Store its secret only in the relay.
Verify HMAC, timestamp, nonce, delivery ID, and event ID there. Forward a
normalized event to
bundle.targetUrl after verification.Direct private prototype
Use direct Zapier subscription only for isolated testing. The returned
secret enters
bundle.subscribeData and may enter Zapier HTTP logs. Never
use this path when that exposure violates your secret policy.Direct prototype subscribe
bundle.subscribeData. Never expose the secret
through trigger output. Use this path only for isolated testing.Unsubscribe
Direct prototype perform
bundle.rawRequest.content before using bundle.cleanedRequest.
Zapier prefixes most inbound raw headers with Http-. Normalize that prefix.Zapier does not provide a durable 5-minute nonce store.
Place a durable verification relay before Zapier in production.
Verify HMAC, timestamps, and nonces there.
Deduplicate deliveryId and streamEventId before forwarding.
Zapier owns responses from bundle.targetUrl.performList, not the live perform handler.