Zapier Setup

Zapier is a powerful ally. Hook up TypeflowAI with Zapier and you can send your data to 5000+ other apps. Here is how to do it.

Nail down your workflow first? Any changes in the workflow cause additional work in the Zap. It makes

sense to first settle on the workflow you want to run and then get to setting up Zapier.

Step 1: Setup your workflow incl. questionId for every question

When setting up the Zap your life will be easier when you change the questionIds of your workflow questions. You can only do so before you publish your workflow.

In every question card in the Advanced Settings you find the Question ID field. Update it so that you’ll recognize the response tied to this question.

Already published? Duplicate workflow You can only update the questionId when the workflow was not yet

published. Already published it? Just duplicate it to update the questionIds.

Step 2: Send a test response

In order to set up Zapier you’ll need a test response. This allows you to select the individual values of each response in your Zap.

Step 3: Setup your Zap

Go to and create a new Zap. Search for “TypeflowAI” to get started:

Then, choose the event you want to trigger the Zap on:

Step 4: Connect TypeflowAI with Zapier

Now, you have to connect Zapier with TypeflowAI via an API Key:

Now you need an API key. Please refer to the API Key Setup page to learn how to create one.

Once you copied it in the newly opened Zapier window, you will be connected:

Step 5: Select Workflow

Next, you can choose from all the workflows you have created in this environment:

Step 6: Test your trigger

Once you hit “Test” you will see the three most recent submissions for this workflow. If you don’t have any submissions in the workflow, submit one to continue setting up your Zap:

Now you're happy that you updated the questionId's

Step 7: Set up your Zap

Now you have all the data you need at hand. The next steps depend on what you want to do with it. In this tutorial, we will send submissions to a Slack channel:

In the action itself we can determine the data and layout of the message. Here, we only choose the submission data. You can also refer to the meta data of the submission and the attributes of the person who submitted the workflow.

We now receive a notifcation in our Slack channel whenever a Churn workflow is completed:

Was this page helpful?