Zapier trigger not passing custom field values

Question

We've got a Zap set up that triggers when a work order status changes. The trigger fires fine, but the custom fields we added to the work order aren't showing up in the payload. Just the standard fields.

Need these values to pass into our CRM. Is this a known limitation or am I missing a configuration step somewhere?

Eli Torres (Staff) · Accepted Answer

Hey Mike — yeah, this one trips people up. The default Zapier trigger payload doesn't include custom fields by design (keeps the initial payload size manageable), but you can pull them in with a second step. After your trigger, add a Get Work Order action from FieldPulse and check the option to include custom fields. That second call returns the full record with everything expanded: {
 "id": "wo_12345",
 "title": "AC Repair",
 "custom_fields": {
 "cf_abc123": "Premium Service Plan",
 "cf_def456": "12345"
 }
} Bit annoying that it takes two steps, but that's the current behavior. We're looking at adding a "rich payload" option to the trigger itself — no timeline yet but it's on the radar. Full walkthrough here: Zapier Integration Guide

Devon Marsh · Answer

Can confirm the two-step approach works. Heads up though — if you're dealing with high volume, that extra API call counts against your rate limit. We hit this with a customer doing ~200 status changes per day and had to be careful about timing.

YMMV but worth monitoring if you're at scale.