This error means Zapier received data from the trigger app but could not interpret it. The trigger returned data in an unexpected format — often HTML instead of JSON, or a data structure that changed after the Zap was configured. Re-test the trigger step to load the latest data structure, and check for API changes in the trigger app.
What does "Error parsing data from trigger" mean in Zapier?
When Zapier shows "Error parsing data from trigger," it means the trigger step received a response from the connected app that Zapier could not convert into usable data. Zapier expects triggers to return structured data (JSON objects), but the trigger returned something it could not parse — typically HTML, XML, plain text, or malformed JSON.
The most common cause is the classic "Unexpected token '<', '<!DOCTYPE'..." error, which means the API returned an HTML error page instead of JSON data. This happens when the API URL is wrong, authentication failed (redirecting to a login page), or the server returned a 500 error page. Zapier tries to parse the response as JSON and fails on the HTML.
Another frequent scenario is a trigger app updating its API response format. If the trigger was configured with one data structure and the app later changed its response (added fields, renamed fields, or changed data types), Zapier may fail to parse the new format. This is especially common with trigger apps that rely on webhooks, where the payload structure is controlled by the sending application.
Common causes
The trigger app returned HTML instead of JSON
usually an error page, login redirect, or 500 server error
The trigger app updated its
API response format after the Zap was configured, changing the data structure
The webhook payload contains newline characters or
unescaped special characters that break JSON parsing
The trigger app's authentication expired, causing
it to return auth error responses instead of data
The trigger is polling an endpoint that
returns empty or null data during certain periods
The trigger response exceeds Zapier's
data size limit for a single trigger event
How to fix trigger data parsing errors in Zapier
Go to the Zap editor and click 'Test trigger' on the trigger step. This loads the latest data from the trigger app and updates Zapier's understanding of the data structure. If the test fails, the trigger app may be returning errors — check the trigger app's status and your authentication. If the test succeeds but the live Zap fails, the issue is likely intermittent data format differences between test and live data.
For webhook triggers, check the Zap History to see the raw data that was received. Look for HTML tags (indicating an error page), newline characters in text fields (which break JSON), or unexpected data types. If the trigger app changed its API, you may need to re-map all fields in subsequent Zap steps. Use Zapier's Troubleshoot tab in the errored run's history for AI-powered diagnosis. For recurring parsing issues with complex data sources, RapidDev can help build a middleware layer that normalizes trigger data before it reaches Zapier.
Prevention tips
- Re-test the trigger step whenever you see parsing errors — this refreshes Zapier's understanding of the data format
- Check the Zap History for the raw trigger response to see exactly what data caused the parsing failure
- Use Zapier's built-in Troubleshoot tab (click an errored run) for AI-powered diagnosis of parsing issues
- For webhook triggers, validate the payload format on the sending side before it reaches Zapier
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
My Zapier Zap shows 'Error parsing data from trigger' with 'Unexpected token < in JSON'. The trigger app is returning HTML instead of JSON. How do I fix this?
Diagnose why my Zapier trigger is receiving HTML instead of JSON data and suggest fixes for the trigger configuration.
Frequently asked questions
What does "Error parsing data from trigger" mean in Zapier?
Zapier received a response from the trigger app that it could not convert to structured data. The response was likely HTML, XML, or malformed JSON instead of valid JSON. Re-test the trigger step and check the trigger app's status.
Why does my Zapier trigger return HTML instead of JSON?
This usually means the API URL is wrong, authentication failed (the API redirected to a login page), or the server had an error and returned an HTML error page. Check your authentication and the API endpoint URL.
How do I see the raw data my Zapier trigger received?
Go to Zap History, click the errored run, and expand the trigger step. The 'Raw Data' section shows exactly what Zapier received. Look for HTML tags, missing fields, or unexpected data types.
Can changes in the trigger app's API cause parsing errors?
Yes. If the trigger app changes its API response format (adds, removes, or renames fields), Zapier may fail to parse the new format. Re-test the trigger to load the new structure and re-map all affected fields.
Does Zapier's Troubleshoot feature help with parsing errors?
Yes. Click an errored run in Zap History and use the Troubleshoot tab. Zapier's AI-powered troubleshooting analyzes the error and suggests specific fixes, which is genuinely useful for parsing issues.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your issue.
Book a free consultation