Connecting Zapier to Stitch is a three-step process:
- Add Zapier as a Stitch data source
- Generate a Webhook URL
- Set up webhooks in Zapier
Zapier is incredibly useful, powerful, and flexible. Because Zapier gives you complete control over how your data is defined and sent, we’ll walk you through the setup using a Zap we use at Stitch every day.
Whenever you provide feedback to us while chatting on Drift, we record it using a Google Form. We set up a Zap that sends new submissions to our data warehouse, where we can analyze them and determine what our top priorities for development are. Additionally, everyone is notified of a new submission via email and a notification in Slack.
Adding Zapier as a Stitch Data Source
- On the Stitch Dashboard page, click the Add an Integration button.
- Click the Zapier icon.
- Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your data warehouse.
For example, the name “Stitch Zapier" would create a schema called
stitch_zapier in the data warehouse. This schema is where all the tables for this integration will be stored.
- Click Save Integration.
Generating a Zapier Webhook URL
Once Stitch has successfully saved and created the integration, you’ll be redirected to a page that displays your webhook URL and token (which is blurred in the image below):
Click the Copy button to copy it.
Note that this particular URL won’t display in Stitch again once you click Continue. Think of this URL like you would your login or API credentials - keep it secret, keep it safe. You can, however, generate another URL should you need it.
Once you’ve copied your webhook URL, click Continue to wrap things up in Stitch.
Setting Up Webhooks in Zapier
Zapier has detailed instructions
that delve into the finer points of making a Zap, but for our purposes, we’ll keep it high-level.
In this example, we’ll demonstrate by walking you through how we set up our product feedback webhook using Zapier and Google Forms.
Defining the Trigger
In this step, you’ll define the event that will trigger the webhook.
- Sign into your Zapier account.
- Click Make a Zap! at the top of the page.
- Select the appropriate app from the Choose a Trigger App page. For us, we chose Google Forms.
- Next, you’ll define the Trigger. We chose to use new responses in our spreadsheet as our trigger.
- Depending on the app you’ve selected, you may be asked to select the account you want to use. Select the appropriate account and click Continue when finished.
- If you want to test the set up before moving on, feel free to do so now.
Defining the Action
Next, you’ll define the action, or what happens once the webhook has been triggered.
- Select Webhooks from the Choose a Trigger App page. It’s in the Built-in Apps section.
- On the Action page, click POST. Note that Stitch Incoming Webhooks only accepts POST requests at this time - if anything else is selected, the integration won’t work.
- Next, you’ll define the template for the Zap:
When you’re finished defining the other options for the template, click Continue.
If you’d like to test the setup so far, do so now.
If you want to add more steps, click the Add a step button. Otherwise, if you’re finished, click Finish.
If your testing was successful and you’re happy with your setup, toggle the Zap to On to get the data flowing.
- In the URL field, paste the Stitch-generated webhook URL.
- In the Payload Type field, select JSON from the drop-down menu. Note that Stitch Incoming Webhooks only accepts data in JSON format at this time - if anything else is selected, the integration won’t work.
- If you choose to, you can define data in the Data section. Note that this section is optional; if left blank then the raw data from the previous step (from the app you chose) will be used instead:
We chose to re-define our form fields here, as using the raw data from the Google Form would result in columns named like this:
gsx$clientid, which we felt wasn’t query-friendly.
Zapier Data & Replication
After the setup for Zapier is complete, your webhook data will be continuously replicated through Stitch. To learn more about how Stitch replicates Zapier webhook data and our recommended strategy for querying, check out the Expected Zapier Data article.