I’m building a custom Zapier integration and running into a frustrating issue. All my setup steps are working fine - the API connection authenticates properly and everything seems to be configured correctly according to Zapier’s documentation.
However, when I actually test the integration, I keep getting this error message: Got a result missing the ‘id’ property
I suspect the problem might be related to how my API response is structured. It seems like Zapier expects the ‘id’ field to be positioned at the top of my response object, but my API sometimes returns the ‘id’ field in different positions within the data structure.
Has anyone encountered this before? How can I ensure Zapier always finds the required ‘id’ property regardless of where it appears in my response?
totally agree! zapiers like super strict about that id field. i had issues when i used variations too. if it’s null, zapier throws a fit so best to ensure there’s always a valid value for it. keep the id at the top and it should work!
You’re right about the position issue, but there’s another culprit I’ve run into. After working with several Zapier integrations, I’ve noticed the problem usually comes from inconsistent data types for the id field, not just positioning. Your API needs to consistently return the id as either a string or number - mixing types breaks things even when the field’s there. Also check your trigger config in the Zapier CLI or developer platform. The sample data you set up initially might not match what your live API actually sends back, so Zapier ends up hunting for the id in the wrong spot. I usually fix the API response structure first, then regenerate the sample data. That clears up the mapping issues every time.
This happens when Zapier can’t find the id field at the root of your response object. JSON structure matters here - Zapier expects certain fields right at the top level. I had the same issue last year with a CRM API that buried the id inside a metadata object. I fixed it by adding a response transformation layer before hitting Zapier. You have two options: modify your API to place id at the top level or use Zapier’s output field mapping to specify where the id is located. Also, check if your API is returning arrays instead of objects, or if the id is being renamed somewhere. Ensure your response sends a flat object with id as a direct property and not nested within other objects.