Zap trigger isn't sending data

You might notice that your trigger app isn't sending any data to your action app, despite your Zap History showing that the Zap has triggered successfully.

1. Check if your fields are mapped

Data may not be sent from one step to another if no data has been mapped over from previous steps. Most apps require that you “map” data, which is to specify which data from previous steps you want to insert or use in the fields in later steps. Zaps cannot do this automatically.

actionEdit icon Example

A static value "laura@example.com" is entered in the Subscriber Email field in a MailChimp action in a Zap. This means that every time the Zap runs, this field will be set to the same email address. If a dynamic value is used instead—an email value from a column in a Google Sheet in a previous step—every time a new row is added to the spreadsheet, the email address in that row will be used in the MailChimp action instead.

2. Check if your mapped fields are pulling empty values

If your data appears to be mapped correctly but the Zap still isn’t transferring it, there might be a discrepancy between the fields you originally mapped in the Zap and the fields that actually exist now that the Zap is running live.

You can check if this is the case by taking a look at a recent Zap run in your Zap History. Check the Data In section of the step that should be bringing data into your app. In this example, you can see that the name field data has curly brackets around it. For example, if you see a field like name: {{2435693_firstName}}, the curly brackets indicate that the field mapped over from the trigger was empty or doesn’t exist in the same way it did when you set up the Zap.

To resolve this issue, load new test data in your Zap trigger, then map the affected fields in your action step(s) again.

If your Zap trigger still isn't sending data after taking these steps, contact Zapier support.

Was this article helpful?
0 out of 5 found this helpful