> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squid-id.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Send visitors to Make

> Send identified Squid ID visitors to a Make scenario through a custom webhook, then fan out to any of Make's apps with the enriched, ICP-gated event.

[Make](https://make.com) is a visual automation platform that chains app modules into scenarios. It's the automation layer, so Squid ID sends the identified visitor straight to a Make webhook and your scenario takes it from there.

## If you're coming from RB2B

Both tools can post to a Make webhook. The difference is the payload: Squid ID's event carries the full work profile, an `is_icp_match` flag, and (when unlocked) Squid ID+ mobile and personal email, so your scenario can branch on real signals.

## Connect

Make's **Custom Webhook** trigger gives you a unique URL that receives the event and auto-detects the fields:

<Steps>
  <Step title="Create the webhook in Make">
    In a new Make scenario, add the **Webhooks → Custom webhook** module and copy its URL.
  </Step>

  <Step title="Point Squid ID at it">
    Use the [Zapier connector](/integrations/zapier) or a [Webhook](/integrations/webhooks) to send identified visitors to that URL. Send a test so Make captures the field shape.
  </Step>

  <Step title="Build the scenario">
    Map the fields into any downstream module: CRM, Slack, enrichment, or an outreach tool.
  </Step>
</Steps>

## What's sent

A flat event with `name`, `email`, `title`, `company`, `linkedin`, `landing_page`, `is_icp_match`, `matched_icps`, and the Squid ID+ fields when the record is unlocked. See the [Zapier payload](/integrations/zapier#what-zapier-receives) for the full list.

## Related

* [Send visitors to Zapier](/integrations/zapier)
* [Webhooks](/integrations/webhooks)
* [Integrations overview](/integrations/overview)