PulseSignal speaks Standard Webhooks v1, the same shape Stripe, Shopify, and Polar use. Zapier's built-in Webhooks by Zapier trigger accepts that shape natively, so you can route change events, narratives, and alert-rule fires into any of the 6,000+ apps Zapier integrates with today. No PulseSignal app install required.
https://hooks.zapier.com/hooks/catch/<account>/<hook>/. Copy that URL.webhook.test payload immediately so Zapier's test panel has a real sample to work with.event_type, data.company_name, data.headline, data.source_url into your destination (Slack channel, Notion database row, Google Sheet append, Salesforce task, HubSpot deal note, whatever the second-step app exposes).The default Catch Hook trigger does not verify webhook signatures, so any caller who guesses your hook URL can inject fake events. For production Zaps that drive money-moving actions (CRM updates, payments, on-call pages), use Catch Raw Hook instead and add a second step that runs Code by Zapier to verify the X-PulseSignal-Signature header against the shared secret you set in PulseSignal. The signing scheme is documented at /help/webhooks with Python and Node reference code.
A short list of second-step apps that pair naturally with PulseSignal events:
A native PulseSignal app on the Zapier marketplace (with per-trigger event types, named output fields, and a discoverable listing in the Zapier directory) is on the roadmap. Until that ships, the generic Webhooks-by-Zapier path above gives you the same delivery guarantees and the same payload shape. If you have a Zap blueprint you'd like us to prioritise, write to hello@pulsesignal.co.