> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/integrations/zapier.md). # Zapier Send quote form data to thousands of other apps through Zapier, without writing any code. Zapier connects apps that do not otherwise talk to each other. If the tool you want is not on the **Third-party integration** list, Zapier is almost certainly the answer — a spreadsheet, a Slack channel, your CRM, an accounting system. {% hint style="info" %} Zapier is listed under the **PRO** plan. Klaviyo, Mailchimp and Shopify are the integrations listed under **FREE**. See [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md). If the controls here are greyed out and a padlock line reads "🔐 This feature is available on …", that is your plan and not a fault. Follow the link in that line, or open **Pricing plans** in the app. {% endhint %} Zapier is the simplest page in the app. There is one field — **Zapier Webhook URL** — and a **Save** button. No API key, no list to pick, no field mapping. All the real work happens on the Zapier side. ## Step 1 — Build the trigger in Zapier Everything in this step happens in your [Zapier](https://zapier.com/apps/webhook/integrations) account. You are building the half of the Zap that listens, so that it has an address the app can send to. {% stepper %} {% step %} ### Create a new Zap In Zapier, select **Create**, then **New Zap**.

Zapier's My Zaps page with the Create menu open and New Zap highlighted — In Zapier, open **Create** and choose **New Zap**.

{% endstep %} {% step %} ### Choose Webhooks by Zapier as the trigger Open the trigger and choose **Webhooks by Zapier**. This is the app that gives you an address to send to.

Zapier's app picker for the trigger, with Webhooks by Zapier highlighted in the built-in tools column — Pick **Webhooks by Zapier** as the trigger app.

{% endstep %} {% step %} ### Choose the Catch Hook event Under **App and Event**, choose the event **Catch Hook**, then select **Continue**. Catch Hook simply receives whatever is sent to it.

Zapier's App and event panel with the event list open and Catch Hook highlighted — Choose the **Catch Hook** event.

{% endstep %} {% step %} ### Enter a Child key Zapier then asks for a **Child key**. Any word will do — it does not have to match anything in the app. Type one and select **Continue**.

Zapier's Trigger tab with a word typed into the Pick off a Child Key field and Continue below it — Any word works as the **Child key**.

{% endstep %} {% step %} ### Copy the webhook address On the test screen Zapier shows a webhook address. Copy it — you paste it into the app next.

Zapier's Test tab showing Your webhook URL with a Copy button beside the address — Copy the address under **Your webhook URL** — the app needs it next.

{% endstep %} {% endstepper %} {% hint style="info" %} You only need the address Zapier produces. Everything after that happens back in your Shopify admin, and then once more in Zapier to finish the Zap. {% endhint %} ## Step 2 — Paste the address into the app {% stepper %} {% step %} ### Open the Integrations tab In your Shopify admin, open **SA Request a Quote**, select **Advanced settings**, then open the **Integrations** tab. {% endstep %} {% step %} ### Select Zapier Under **Third-party integration**, select **Zapier** — described in the app as "Automate your workflow by connecting apps together".

The Integrations tab of Advanced settings with Zapier outlined in red — Zapier is how you reach a service the app does not list.

{% endstep %} {% step %} ### Paste it into Zapier Webhook URL Paste the address you copied into the **Zapier Webhook URL** field. It is the only field on the page.

The Zapier integration page showing its single Zapier Webhook URL field filled in, with the Save button — One field, one button: paste the address and select Save.

{% endstep %} {% step %} ### Save Select **Save**. Quote submissions now go to that address. {% endstep %} {% endstepper %} {% hint style="warning" %} Treat the webhook address like a password. Anyone who has it can push data into your Zap. {% endhint %} ## Step 3 — Send Zapier some test data {% stepper %} {% step %} ### Submit a quote Go to your storefront and submit a quote request as a customer would.

{% endstep %} {% step %} ### Test the trigger in Zapier

Zapier's Test tab with the webhook address shown and the Test trigger button beneath it — **Test trigger** asks Zapier to look for your submission.

Back in Zapier, select **Test Trigger**. Your quote data appears, and Zapier now knows the shape of it. {% endstep %} {% step %} ### Continue with the record Zapier found Select **Continue with selected record**. Zapier keeps that submission as the example it matches your fields against for the rest of the Zap.

Zapier's test result listing the captured quote record, with the Continue with selected record button below it — Select **Continue with selected record** to lock in the example.

{% endstep %} {% endstepper %} {% hint style="warning" %} Submit your test quote with every field filled in. Zapier learns your data structure from this one example, so fields you leave empty may not be available to match later. {% endhint %} ## Step 4 — Choose where the data goes Now pick the app that receives it. Zapier supports thousands; a spreadsheet is a common first choice because it is easy to check. Inside Zapier, select your app and the action you want, sign in to that app when Zapier asks, complete the steps on the **Action** tab so the quote fields line up with that app's fields, and turn the Zap on. This matching is a Zapier step — there is nothing to map back in the Shopify admin.

Zapier's app picker for the action step, with Google Sheets highlighted — Google Sheets, as the worked example.

Zapier's action step connected to Google Sheets, with the spreadsheet fields being chosen — Point the action at your spreadsheet.

Zapier's field mapping for the Google Sheets action, with quote fields lined up against spreadsheet columns — Each quote field lands in its own column — this mapping happens in Zapier, not in the app.

## What people use this for

Destination	Why
Google Sheets	A running log of every request, easy to filter and share.
Slack or Teams	The team sees new quotes immediately without watching an inbox.
Your CRM	Quote leads land in the same pipeline as everything else.
Accounting software	A head start on invoicing for quotes you expect to win.

{% hint style="success" %} A Slack notification is the quickest win. Quotes are time-sensitive, and a channel message gets acted on faster than an email. {% endhint %} ## If nothing reaches Zapier * **Check you selected Save.** The address is not live until you do. * **Check the address is complete.** A truncated paste fails silently. * **Check the Zap is turned on in Zapier.** A Zap left in draft receives test data but does nothing with real submissions. ## Next steps * [Integrations overview](/sa-request-a-quote/integrations/overview.md) — the providers you can connect directly, no Zapier needed * [Emails sent to admin](/sa-request-a-quote/emails/emails-to-you.md) — get told about new quotes without a third-party tool * [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md) — what the PRO plan includes --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.samita.io/sa-request-a-quote/integrations/zapier.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.