There's a wide range of reasons that a Zap can come back with an error. We do our best to provide actionable error messages, but sometimes there's too many potential problems or an app's error messages are vague, leaving you to wonder what went wrong. Here's some steps you can take to get to the bottom of the problem:
We have a guide on common error messages here.
Your task history is a log of all the tasks your Zap has attempted on your behalf, you can access it from this link or from your dashboard. While the task history won't show a record of tests made when configuring your Zap, or errors in connecting to your trigger, it's invaluable to identifying errors when your Zap tried to complete its action.
You can click on the "Data In" and "Data Out" buttons for both your Trigger and Action apps to see what data we received and sent on.
For more information on using the Task History to debug trouble with your Zap, please see our Task History Guide here.
Many errors can be corrected with just a small change to the configuration of the Zap, especially the Action template. We go over some common scenarios here, but here's some things to look out for in general:
Sometimes your Zap is working successfully, but it may be creating data in a place you weren't originally expecting. Especially if you're creating something that belongs under another object(like how a Task may belong to a specific Project), check your Zap to make sure the destination you've chosen in your Zap matches where you're looking for that data in that app.
Some errors are a result of oddities in how a particular app behaves. We do our best to document those in our Service Documentation, so check that out for the app involved to make sure there's not an easy fix waiting for you!
When mapping action fields, you'll see the fields that the action app is telling Zapier are required to perform that action.
Make sure that the fields you choose to include from the trigger app will always have data in them. If they are ever empty, then the Zap will very likely create an error.
If you're okay with trigger data not always being included, there are a couple potential workarounds:
NOTE: These workarounds may not apply universally: some apps have more strict requirements about the values that can be used, as well as varying degrees of acceptance for duplication. Also, if there is more than one required field where this is an issue, the 2nd workaround will require several Zaps to account for all the potential outcomes. We don't recommend that 2nd workaround if there's more than one required field with a risk of empty data in the trigger.
Dropdowns show possible values to be used within fields.
Often the choices are dependent on some specific criteria, like the value of a previous dropdown. Sometimes choices are dependent on the account you've connected because choices may be dependent on your account's permissions.
If you're seeing empty choices, make sure the account you've connected has the necessary permissions to show all of the desired choices, and make sure that any criteria you have set up in your zap that may be filtering out choices is set up appropriately.
For example on the screenshot below this "list" dropdown doesn't have any options, as I don't yet have any lists on that particular Trello board:
If I add a list to that board on my Trello account, that will then appear in that dropdown on my Zap template like this:
If you use any filters in your Zap, especially custom filters, make sure that you understand the logic those filters are using. There are two easy ways to check on your filters:
In both instances, you should see a reference to which filter(s) is stopping that task from proceeding. Here are a couple other common issues people run into with filters:
If your Zap is creating an event, or taking a date from an event to send somewhere else, here's some common fixes that can avoid errors:
Sometimes you may find you don't want to use a fixed values in a drop down but using a custom value can cause errors if it doesn't match up with what your app is expecting. To avoid that please follow our guide here.