Capture the trigger payload
Compare the visible Zap sample with the field the source app actually provides, including nested or recently added custom fields.
Zapier custom-field trigger debug
For Zapier workflows where the trigger fires, but a custom field is missing, renamed, nested, stale, or mapped to the wrong downstream step.
Operating plan
Compare the visible Zap sample with the field the source app actually provides, including nested or recently added custom fields.
Separate field refresh issues, renamed fields, blank values, and fallback behavior before editing downstream actions.
Leave the expected field list, exception path, and launch checks so customer, order, or CRM records are not silently wrong.
Related paths
Ready to start