# Zapier Like [Segment](/integrations/integration-reference/segment.md), [Zapier](https://zapier.com/) is a dynamic integration option to store and send data from Formsort to other Apps. As long as an app is found in Zapier's library, you can use Zapier to seamlessly stream data collected from Formsort forms. That said, we currently do not support direct implementations with Zapier. However, it is simple and effective to integrate with Zapier through a Webhook! Follow the **setup** below to do just that! ## Setup ### Step 1: Create Zap with Webhooks as the first trigger. Adding Webhooks as the first trigger for your Zap will give us the ability to send requests to Zapier through a Webhook integration, within the Formsort platform (more below on how to formally setup this integration). ![Create Zap with Webhooks as first trigger](/files/EnzEOH14CU2fSW8SBS7y) ### **Step 2. Choose a Trigger Event** The **Trigger Event** is what occurs once the Webhook receives a request from Formsort. This field has two relevant options, **Catch Hook** and **Catch Raw Hook**. These trigger events differ as follows: * **Catch Hook** parses individual fields from the body of the Formsort POST request. This allows you to customize exactly which fields you pass to other apps, and how you structure those fields. * **Catch Raw Hook** leaves the JSON request as-is, and includes all fields, including headers. Data can only be sent to other apps in that raw format. ![Step 2: Choose a Trigger Event](/files/-ManvDMKwmybXQ2Ld2Wa) {% hint style="info" %} Most users will want to choose the **Catch Hook** option. You'll use this option whenever the data needs to be easily comprehensible to human readers. If, for example, you wanted to pass the data to an email or a CMS, this option would serve your needs. If, however, you do want to preserve the response completely intact, **Catch Raw Hook** would be the preferred option. For the rest of this walkthrough, we will assume the user chooses **Catch Hook** {% endhint %} ### Step 3: Integrate Webhook in Formsort Now, we need to enable this Webhook within Formsort. First, copy the Custom Webhook URL from the **Set up trigger** option in Zapier. ![Copy Custom Webhook URL](/files/-ManvdA2_DrwDXCRpS5l) In Formsort, navigate to the Integrations tab for your flow (found at the Flow level, not at the Variant level), and then to the Webhooks option. Choose a [Webhooks](/integrations/integration-reference/webhooks.md) posting frequency, then copy the **Custom Webhook URL** into the **Webhook URL** field: ![Paste Custom Webhook URL into Form: Integrations --> Webhooks --> Webhook URL](/files/8VDAQQXwt0Y7uK8kdl5P) {% hint style="warning" %} If you receive a message that hooks.zapier.com cannot be added as a Webhook, be sure to add the 'hooks.zapier.com' domain in Account --> Security --> Allowed Webhook destinations --> + ADD ANOTHER DOMAIN. {% endhint %} ![](/files/-Mao3Q95gOyncdxG92sA) ### **Step 4. Send test request to Zapier** Use **Send Test** from the Formsort Studio to send a request to the Webhook URL. ![Send Test to Zapier Webhook](/files/-Mao6SMO7yrrp6XIBW_V) ### **Step 5: Test trigger** Back in Zapier, continue to the **Test trigger** option, and enable a test. Assuming you successfully sent the test to the Webhook from Formsort, the Zapier Webhook should successfully have found a request that contains fields found in the Formsort payload. These should contain fields like `answers`, `responder_uuid`, and `variant_uuid`. And, that's it! Your Zap is now ready to receive data from Formsort, through a Webhook. All that's left to now is to connect your Zap with other apps! ![hint](/files/-MaoPFJLi71YppaTOWav) {% hint style="info" %} After you've connected to Zapier via Webhook, if you have deployed flows previous to the integration, it is advisable to re-[deploy](/core-concepts/versioning-in-formsort-deploying.md) those flows. {% endhint %} ### **Step 6: Customize data sent from Formsort to other apps** At this point, you will add additional Apps to your Zap to receive form submission data from Formsort. While it is impossible to walk through every possible app you could integrate with, you will find all the individual fields parsed from the body of the Formsort request available in the **actions** for other apps. Using Slack as an example, the following screenshot shows that individual fields from the form submission data can be accessed and used for any Slack **action**: ![Sending form submission data to Slack through Zapier](/files/-MaoTVPCoGea1xlK3e80) ### **Step 7: Turn on your Zap!** Now that your Zap is ready to receive data from Formsort through a Webhook, and you have other apps integrated into your Zap that will receive Formsort form submission data, it's time to turn your Zap on! You will first need to test whatever **actions** you setup in Zapier, then you will be prompted to enable your Zap. ![Zapier On/Off toggle switch](/files/-MaoWAfqOcFBmNLS6SD8) {% hint style="info" %} If you do not turn your Zap on, then data from published Formsort form flows will not be received. Do not confuse the fact that your Zap receives requests from 'Send Test' {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.formsort.com/integrations/integration-reference/webhooks/zapier.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.