How Testing Your Zap Works#

Testing your steps is an important part of setting up your Zap. In this guide we'll talk about how the different test stages work and why they are important to your Zap's setup.

What Does Testing do?#

  • Testing your trigger pulls in a sample for us to use when you set up your action.
  • Filter tests show you how your filter would work if your Zap was live.
  • Testing your action step enables you to perform that action to make sure your Zap is working as expected.

Testing Behavior#

  • Testing your Zap data runs from top to bottom. So if you re-test your trigger, to pull that data through to your bottom step you will need to retest each step from top to bottom to bring down the data.
  • Therefore, if you add a step in the middle of you Zap, you will need to retest any later steps after your new one.

Testing your Trigger#

Testing your trigger will pull in an example of what you want to trigger your Zap. This will either be sample data set by the app, or a very recent trigger that happened on your app. For example if your trigger is "Typeform New Entry," the trigger test will bring in a recent submission from your form.

Tip - if we can't find a result right away, we might need a more recent sample. So try performing the trigger in your app and the retesting this stage.

Previewing your Data during setup#

You can easily test that the data you're populating in your template is correct by using the Preview Toggle.

The Preview Toggle is available in any action or search step. To use it slide it back and forth to toggle between fields and values in your template.

Testing your Action#

Testing your action will actually perform the job your action is set to do. So if my Action is "Gmail Send Email", my action test will actually send an email.

It will use the data based on your trigger and any other previous steps. So if your action test fails as a required field is missing, it may be that you need to do a new trigger test.

Before we test your action, we will show you a summary of what will be sent. Like this:

If you see a field rather than an answer on this page, that means we do not have anything from the trigger to send on here.

In the example above, it looks like the form submission from the Trigger test didn't have an email address filled in that field, so we have no email to send an email to. As there is no email, this test will result in an error (it's not possible to send an email without an email address to send it to).

You'll want to retest your trigger to make sure the missing field is present so you can retest your action successfully, or if you are confident your Zap will work from now on you can skip this action test and turn on your Zap.

Testing your Filters#

Testing your filter is a little different as the test cannot fail here. It either shows you if you Zap would have continued to the next step or would have been filtered based on your Trigger and filter criteria.

In this example, the filter is looking the ice cream flavor to be chocolate AND for an email address to exist:

So if we test this filter, it is showing us that in this instance your Zap would not have continued to the next step as even though an email address exists, the ice cream flavor from the trigger test was vanilla:

This is only so you can see how your filter will function when live. If the sample data would not have continued and it's not supposed to continue based on the conditions you've set, your filter is mostly likely working and you can continue onto the next step of your Zap.

↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help