> For the complete documentation index, see [llms.txt](https://docs.webstudio.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.webstudio.is/university/integrations/zapier.md).

# How to integrate Webhook Form with Zapier (deprecated)

Connect Webstudio forms to Zapier for workflow automation.

{% hint style="info" %}
**Deprecated:** This guide uses the [Webhook Form](https://docs.webstudio.is/university/core-components/webhook-form.md). Use [Form](https://docs.webstudio.is/university/core-components/form.md) for new forms.
{% endhint %}

{% embed url="<https://youtu.be/FDm4mz5FBD8>" %}
How to integrate Webstudio with Zapier
{% endembed %}

Zapier allows you to connect Webstudio forms to thousands of apps, automating workflows like adding contacts to your CRM, sending notifications, or creating spreadsheet entries.

## What You'll Need

* A Webstudio project with a [Webhook Form](https://docs.webstudio.is/university/core-components/webhook-form.md)
* A [Zapier account](https://zapier.com) (free tier available)

## Step-by-Step Guide

### 1. Create a Zap in Zapier

1. Log in to Zapier and click **Create Zap**
2. For the trigger, search for and select **Webhooks by Zapier**
3. Choose **Catch Hook** as the trigger event
4. Click **Continue** – Zapier will generate a unique webhook URL
5. Copy this webhook URL

### 2. Configure Webstudio

1. In Webstudio, select your Webhook Form component
2. Go to Settings and paste the Zapier webhook URL into the **Action** field
3. Publish your site

### 3. Test the Connection

1. In Zapier, click **Test trigger**
2. Go to your published Webstudio site and submit the form
3. Return to Zapier – it should detect your test submission
4. You'll see all the form fields available for use in your Zap

### 4. Set Up Your Action

1. Click **Continue** to set up what happens after form submission
2. Choose your destination app (Gmail, Google Sheets, Slack, HubSpot, etc.)
3. Map the form fields to the action fields
4. Test and turn on your Zap

## Common Use Cases

| Destination        | Use Case                        |
| ------------------ | ------------------------------- |
| Google Sheets      | Log all form submissions        |
| Mailchimp          | Add subscribers to email lists  |
| Slack              | Get notified of new submissions |
| HubSpot/Salesforce | Create CRM contacts             |
| Gmail              | Send custom confirmation emails |
| Notion             | Create database entries         |

## Related

* [Webhook Form](https://docs.webstudio.is/university/core-components/webhook-form.md) – The form component used to send data to Zapier
* [Pabbly Integration](https://docs.webstudio.is/university/integrations/pabbly.md) – Alternative with flat-rate pricing for high volume
* [n8n Integration](https://docs.webstudio.is/university/integrations/n8n.md) – Open-source workflow automation platform
* [Airtable Form Integration](https://docs.webstudio.is/university/integrations/airtable-form-webhook.md) – Send form submissions directly to Airtable


---

# 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.webstudio.is/university/integrations/zapier.md?ask=<question>&goal=<user_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.
