Connect Spiderlook to Zapier with webhooks
Connect Spiderlook to Zapier with webhooks and the API so your Zaps can alert the team or update CRM when rival activity changes.
How do I connect Zapier?
In Zapier, add a Catch Raw Hook (Webhooks by Zapier) trigger and copy the custom webhook URL. Catch Raw Hook keeps the raw body and headers, which you need to verify X-Spiderlook-Signature. Catch Hook alone is not enough for signature checks.
In Spiderlook Settings, then Integrations, paste the URL, select events, and store the signing secret your Zap will use in a Code step to validate deliveries.
Send test from Spiderlook so Zapier captures a sample payload. Map entity, item, and deep_link into later Zap steps.
- Create a Catch Raw Hook in Zapier and copy the URL.
- Add the URL in Spiderlook Settings, then Integrations.
- Pick events such as new_meta_ad_detected or new_social_post_detected.
- Send test so Zapier learns the sample shape.
- Add an API request step with your Spiderlook token when you need more detail.
What can I automate?
- Send new rival Meta ads to Slack or Microsoft Teams with deep_link.
- When entity.ready fires, create a HubSpot or Salesforce task so sales can review the new landscape entry.
How do I use an API token for follow-up calls?
Create a token in Settings, then Integrations. In a Zapier Webhooks or Code step, send Authorization: Bearer <token> to the Spiderlook API using the organization slug from the Catch Raw Hook payload.
Call GET /v1/organizations/{slug}/ads, /social-posts, /website-changes, /battlecards, or /tracked-companies for the detail you need after the event.
Organization API keys (crorg_) work well for shared Zaps. Personal tokens (crpat_) fit individual workflows.