Wire PulseSignal into Zapier
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.
4-step setup
- Create a new Zap in Zapier and pick Webhooks by Zapier as the trigger app. Choose the Catch Hook event. Zapier will mint a unique URL of the form
https://hooks.zapier.com/hooks/catch/<account>/<hook>/. Copy that URL. - Add the URL to PulseSignal at Settings → Webhooks. Paste the Zapier URL, pick the event types you want forwarded (change_event, narrative, alert_rule_trigger), and save. PulseSignal will fire a
webhook.testpayload immediately so Zapier's test panel has a real sample to work with. - Map fields in Zapier. In the second step of your Zap, pull the sample payload through and map fields like
event_type,data.company_name,data.headline,data.source_urlinto your destination (Slack channel, Notion database row, Google Sheet append, Salesforce task, HubSpot deal note, whatever the second-step app exposes). - Turn the Zap on. From here, every PulseSignal event of the subscribed type flows through within seconds of the underlying signal being captured. You can verify deliveries from the webhook history table in PulseSignal. Every attempt is logged with its HTTP status code and response body.
Verifying signatures (optional but recommended)
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.
Common destinations
A short list of second-step apps that pair naturally with PulseSignal events:
- Slack / Discord / Teams. Post change events to a sales-intel channel (use this if you don't want to wire our native Slack/Teams integrations directly).
- Notion / Airtable / Coda. Append a row per event for downstream analyst review.
- Salesforce / HubSpot / Pipedrive. Attach competitor activity to the relevant account or opportunity.
- Google Sheets / Excel. Log a timestamped row for ad-hoc reporting.
- PagerDuty / Opsgenie / Linear. Page on critical alert-rule fires, file tickets for repeat patterns.
Native Zapier app
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 prioritize, write to hello@pulsesignal.co.