> ## 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 Zapier

> Send identified Squid ID visitors to Zapier as a flat event you can map into any of Zapier's thousands of apps, with ICP routing, requirements, frequency, and Squid ID+ data.

When a visitor is identified, Squid ID can send them to Zapier as a flat JSON event. From there a Zap can route them into any app Zapier connects to. You paste a Zapier webhook URL, choose which visitors send and how often, and the fields arrive ready to map.

## If you're coming from RB2B

RB2B has a Zapier app with a single "New Profile" trigger and a repeat-visit toggle, and it does not document the fields it sends. Squid ID gives you the fields up front, plus the targeting and depth its trigger lacks.

<div className="compare">
  <table>
    <thead>
      <tr><th /><th>RB2B</th><th>Squid ID</th></tr>
    </thead>

    <tbody>
      <tr><td>Connect</td><td>Zapier app + two API keys</td><td>Paste a Catch Hook URL</td></tr>
      <tr><td>Fields documented</td><td>Not published</td><td>Flat, named, previewed in-app</td></tr>
      <tr><td>How often</td><td>Net-new, or every visit</td><td>Net-new, or every visit (<code>is\_repeat\_visit</code>)</td></tr>
      <tr><td>Who sends</td><td>All visitors</td><td>All, by ICP, or by high-intent page</td></tr>
      <tr><td>Requirements</td><td>Not available</td><td>Require company, LinkedIn, or work/personal email</td></tr>
      <tr><td>ICP signal for Zap filters</td><td>Not provided</td><td><code>is\_icp\_match</code> boolean + <code>matched\_icps</code></td></tr>
      <tr><td>Premium contact data</td><td>Not provided</td><td>Mobile, personal email, address via <a href="/add-ons/squid-id-plus">Squid ID+</a></td></tr>
    </tbody>
  </table>
</div>

<p className="why"><strong>Why this matters.</strong> A Zap is only as good as the data and the filtering you give it. Squid ID sends a clean, flat record with an ICP-match flag and unlocked contact data, so your Zap can branch on intent and act on a mobile number, not just forward an anonymous-ish lead.</p>

## Before you start

<Info>You'll move faster if these are already in place.</Info>

* You're an **Owner** or **Admin** on the website. Viewers can see the connector but can't change it.
* The [snippet is installed and verified](/getting-started/install-snippet), so there are visitors to send.
* A Zap with a **Webhooks by Zapier** trigger, so you have a Catch Hook URL to paste.

## Connect Zapier

<Steps>
  <Step title="Create the Catch Hook in Zapier">
    In Zapier, create a Zap and choose the **Webhooks by Zapier** trigger with the **Catch Hook** event. Copy the custom webhook URL it gives you.
  </Step>

  <Step title="Paste the URL">
    In Squid ID, go to **Settings → Integrations** and click **Connect** on the Zapier card. Paste the webhook URL.
  </Step>

  <Step title="Send a test event">
    Click **Send test event**. A sample record posts to your Zap so Zapier can read the fields and you can map them.
  </Step>

  <Step title="Set who and how often, then save">
    Choose the frequency, routing, and requirements (below), then **Save**. Qualifying visitors now flow to your Zap.
  </Step>
</Steps>

## Choose who sends

* **Send.** *Once per visitor* (the default) sends one event the first time we identify a person; *every identified visit* re-sends on return visits and adds `is_repeat_visit: true`.
* **Who.** Route *all identified visitors*, *any [ICP](/finding-visitors/icp-filtering) match*, *only specific ICPs*, *any high-intent page*, or *only specific high-intent pages*.
* **Only send when.** Require a company, a LinkedIn profile, or a work or personal email before an event is sent.

## What Zapier receives

A flat object with named, mappable fields. The connector preview shows the exact shape. Standard fields:

`event`, `captured_at`, `name`, `first_name`, `last_name`, `email`, `title`, `linkedin`, `location`, `company`, `company_domain`, `company_website`, `company_industry`, `company_size`, `landing_page`, `referrer`, `is_icp_match`, `matched_icps`, `is_repeat_visit`, `squid_profile_url`.

When the record is unlocked through [Squid ID+](/add-ons/squid-id-plus), the event also includes `mobile_phone`, `personal_email`, `phone_numbers`, and `home_address`.

<Info>Squid ID+ fields are sent only for records that are unlocked, either because the website is on [Squid ID+ Automatic](/add-ons/squid-id-plus#turning-on-automatic) or the record was revealed. For other records, only the standard fields are sent.</Info>

## Ideas to build

* **Filter by intent.** Add a Zapier filter on `is_icp_match` is true, then route only on-profile visitors into your sequence.
* **Branch by page.** Use `landing_page` contains `/pricing` to fork high-intent visitors to a different path.
* **Call when there's a mobile.** A path that only runs when `mobile_phone` exists can trigger a task or an SMS step.

## Pause or disconnect

* **Pause:** Use the toggle on the Zapier card to stop sending without losing the webhook URL or settings.
* **Disconnect:** Open the connector and click **Delete**.

## Related

* [Send visitors to Clay](/integrations/clay)
* [Webhooks](/integrations/webhooks)
* [ICP filtering](/finding-visitors/icp-filtering)
* [Squid ID+](/add-ons/squid-id-plus)