When setting up a Zap, Bubble's test trigger and live trigger use different keys for your data fields. The test trigger pulls data via the Data API — which returns records using underlying field IDs as keys. But when the Zap runs live, Bubble sends data using field display names as keys. That mismatch causes Zapier to misread incoming fields as missing, which prevents your Zap from completing successfully.
What you might notice
Your Zap test passes, but the live Zap fails with field errors
Fields in live Zap runs appear missing or unrecognized
Zapier workflow history shows errors after a trigger fires from your live app
Workaround
In your Bubble app, go to Settings → API and check the "Use field display instead of ID for key names" option. This makes the test trigger return field display names — matching what Bubble sends when the Zap fires live — so both sides stay in sync.
For more on setting up Zapier with Bubble, see the Zapier article.
Status
We're aware of this inconsistency. A fix would require careful planning to avoid breaking existing Zapier or Data API setups, so we don't have a timeline yet. The workaround above resolves the issue for most cases.