Zap is not sending data

Written by Owner

Updated at August 20th, 2025

+ More

Table of Contents

Causes Fields do not contain static values or mapped fields Mapped fields do not contain data Mapped fields no longer exists in the app Identify the root cause How to fix it Still need help?

When your Zap is on, you might notice that:

Your trigger is not sending data to your action steps, despite your Zap history showing that the Zap has successfully triggered.
Data from one action step is not being sent to subsequent action steps.

Causes

This can happen for a few reasons:

Fields do not contain static values or mapped fields

Fields do not contain static values or mapped fields

Zapier only transfers data that is entered or mapped from previous steps. For most apps, you must select values from prior steps to insert into later actions, a process called field mapping. This lets the Zap know what data should go on each field.

Mapped fields do not contain data

Mapped fields do not contain data

If your Zap is not transferring data even after correctly mapping information from a previous step, the issue may be that the field you have mapped has no data.

This can happen if:

The field was left blank by the person entering information.
Data is coming through a different field.

Mapped fields may no longer exist in the app

Mapped fields no longer exists in the app

If a mapped field no longer exists or its name has changed, the Zap will not be able to find that data. This can happen if the app renames a field or if you have the ability to customize field names.

Examples

A question used as a mapped field was deleted from a form.
An app, like a CRM, renamed a field (e.g., “Name of Customer” changed to “Customer Name”.

Identify the root cause

In your Zap history, click your affected Zap run. The Zap run will open in the Zap editor.
Click your affected step.
The Run details tab will display what data was received and sent.
- The Data In tab shows data that was sent to the connected app.
- The Data Out tab shows data that was received from the connected app.
Click the Configure tab.
If a mapped field is displayed with the exclamation symbol and a yellow border, this indicates that either:
- The mapped field contained no data at the time the Zap ran.
- The field no longer exists in the app.

How to fix it

In all scenarios, you will need to either add in static values or remap fields.

To remap the fields:

Find new records by testing your Zap step. This will ensure you have the most current fields available.
Once you have new test records, review their content to ensure the fields match your expectations.
If fields do not match:
- Review the process or team responsible for data entry to ensure the correct fields are being populated.
- Review any automations to ensure they populate the fields you're expecting.

Still need help?

If this article did not fix the issue, Zapier has a few other options to get you the help you need:

Contact Zapier Support. Our Support team can investigate your account to find solutions.
Ask in the Zapier Community. Get advice from experienced Zapier users in the Zapier Community.
Learn more about getting help. Read our guide on how to get help and support with Zapier to find the best resources for your specific problem.