Connect Spiderlook to Make with webhooks
Connect Spiderlook to Make with webhooks and the API so new rival ads, posts, and scans can update Slack, CRM, or sheets automatically.
How do I connect Make?
Create a Custom webhook (or HTTP module that receives webhooks) in Make and copy the URL. In Spiderlook, open Settings, then Integrations, add that URL, pick the events you care about, and save the signing secret.
Send a test from Spiderlook, confirm Make receives the payload, then map fields such as entity name, item.channel, and deep_link into the rest of your scenario.
- Create a webhook receiver in Make and copy the URL.
- Add the URL in Spiderlook Settings, then Integrations.
- Pick events (for example new_meta_ad_detected).
- Send test, then continue the scenario with the payload.
- Use a Spiderlook API token for follow-up reads on /v1 when you need more detail.
What can I automate?
- When a rival launches new Meta ads, post a Slack alert with the rival name and deep_link.
- When scan_completed fires, create or update a CRM note for the account team with the Project and entity.
How do I use an API token for follow-up calls?
Create a personal access token (crpat_) or organization API key (crorg_) in Settings, then Integrations. In Make, add an HTTP module after the webhook with Authorization: Bearer <token> and call the Spiderlook public API for the organization in the payload.
Use GET /v1/organizations/{slug}/ads, /social-posts, /website-changes, /battlecards, or /tracked-companies when the webhook payload is not enough.
Keep the token in Make credentials storage. Prefer organization API keys for shared team scenarios so the connection keeps working when people leave.