And it sparkled some hope for me. Does this mean that now I can publish new items via Zapier automatically without a need to log in and do it manually so that the recently added items would be published?
If so would it require some changes in the Zap API?
I’ve just tried to pull some of my CMS items via Zapier, but they have only been staged for published as usual but not published completely.
There are some restrictions on live publish to prevent issues where your live site and your staging site (what you see in the designer) are no longer compatible with each other.
In this case, what this means is that all of the domains you have published to must all be on the same version (published at the same time). Once you republish your site to all publish targets at the same time, the error should go away.
Hm, I’ve just published my sites to all domains at the same time, all the items in all collections are in the status of “Published” but I’m hitting the same error. Tried recreating the Zap from scratch, but still same
Hey all. Still haven’t figured both issues with wrong Time string and error 400. I don’t think there is an error on my side, seems like there are some glitches in new Live CMS app on Zapier. thx @brjohnson@samliew@nathan
I’m running into this issue now as well. All the domains have been published together. I’ve even unpublished it, and then republished them all together. No dice. Here’s the error from Zapier…
Bargle. We hit an error creating a item. Error: api.webflow.com returned (400) Bad Request and said “To directly publish CMS items, your staging and public-facing Collections must be consistent, so be sure to publish to all domains.”
Hi, I’m getting this error as well. Bargle. We hit an error creating a item. Error: api.webflow.com returned (400) Bad Request and said “To directly publish CMS items, your staging and public-facing Collections must be consistent, so be sure to publish to all domains.”
I created a webflow zaps before with no problems so i’m not sure why i’m having this problem now. All the connections are correct. Any help would be appreciated.
@MrCannon@md673 - Can you confirm you are still seeing these errors? This should have been fixed so if you still are experiencing issues with it we will make sure to mark that as a high priority bug and get it fixed right away.