Hi @EverilOrrLiving 

Can you please clarify your question?

Hi @Troy Tessalone,

Sure. I’m using the above Zap to retrieve a file url from a Webflow CMS item with the Webflow API Request, and then include that file in an outbound email.

When the Webflow CMS item is updated with a new file, the new file is what should be included in the outbound email. Instead, the Webflow API Request is not receiving this updated data. And therefore my outbound email is sending an old file that is no longer associated with the Webflow CMS item.

I am trying to figure out why the change to the CMS item is not being reflected in the Webflow API Request.

Thanks

@EverilOrrLiving 

Data is cached for a bit in Zap requests.

Try pulling a different item.

Try turning the Zap ON and testing live.

Thank you @Troy Tessalone 

Perhaps it is a caching issue - I’ve tried both of your above suggestions, as well as deleting the CMS collection entirely and using a new one with a new CMS item. I’m having the same issue, when updating the file in the CMS item, and triggering the zap, the old file is what’s being pulled.

Is the data cached for up to multiple hours/days?

Cheers

@Troy Tessalone for reference if it helps, in the below images are:

1. My CMS item that I’m pulling
2. My Webflow API Request
3. My Outbound Email

Note that the CMS item in Webflow ends with V3.1.pdf but the data in Zapier coming from the API Request in the Outbound Email ends with V3.pdf - this is the old pdf before changing the file in the Webflow CMS. The published update is not being pulled by Zapier?

Thank you

@EverilOrrLiving 

Thoughts…

Caching on the Zapier side is up to 15 minutes I believe, but don’t quote me.

There could also be  a caching issue on the Webflow CMS API side.