Connect Spiderlook to n8n with webhooks
Connect Spiderlook to n8n with webhooks and the API so workflows can notify channels or update systems when rivals change.
How do I connect n8n?
Add a Webhook node in n8n, set it to POST, and copy the production URL. In Spiderlook Settings, then Integrations, add that URL, choose events, and keep the signing secret for a Crypto or Code node that verifies X-Spiderlook-Signature.
Use Send test, then branch on X-Spiderlook-Event or body.entity_type to route Meta ads, social posts, and scan completions into different paths.
- Create a Webhook node in n8n and copy the URL.
- Add the URL in Spiderlook Settings, then Integrations.
- Pick the events your workflow should handle.
- Send test and verify the signature before enabling the workflow.
- Call the Spiderlook API with a stored token for richer follow-up reads.
What can I automate?
- Post new_meta_ad_detected to Slack or Discord with rival name and deep_link.
- When website_change_detected fires, open a ticket or Notion row for the marketing team with Project and entity context.
How do I use an API token for follow-up calls?
Store a Spiderlook personal access token or organization API key as an n8n credential. After the webhook fires, add an HTTP Request node with Authorization: Bearer <token>.
Call GET /v1/organizations/{slug}/ads, /social-posts, /website-changes, /battlecards, or /tracked-companies for the ids in the payload.