Hello make-community!
I’m having problems with the Webflow-module “create an item”: It only creates an item in the primary locale. But I need it to create an item in each of the two locales.
How can I create an item in a CMS collection across multiple corresponding locales using the Webflow create an item module?
Thanks in advance and best regards
Dylan
Hi @dcknoerr,
Welcome to the Make Community. As far as I know, you cannot use the default ‘Create an Item’ module to create items for other locales than your default locale.
You’ll have to use the ‘Make an API Call’ module in combination with this endpoint: Create Localized Collection Item(s) — Webflow API Documentation (I haven’t used this, just sharing the docs)
Cheers,
@Henk-Operative
Hoi Henk! Thanks for your warm welcome and your fast answer. I will then do my best to make a proper api call. Have a nice weekend, Dylan
Hi Dylan,
I believe the endpoint I shared is for creating staged items. I see there is also an endpoint for creating live items directly, which seems to accept a cmsLocaleId propterty. (Create Live Collection Item(s) — Webflow API Documentation)
Please let us know what worked for you!
Kind regards,
@Henk-Operative
Hey Henk, thanks for your addition. Unfortunately, I’m getting [404] Route not found RuntimeErrors all the time:
The path/id to my collection is correct as tested in the playground of the webflow developers reference. I also found similiar problems here within the community, but the answers did not work for me - maybe I’m just missing sth.
The rest of the call also seems fine to me:
Do you have any idea? Thanks in advance!
That’s strange indeed.
As I see in your screenshot, you have the URL /collections/{id}/items/bulk. Normally, Make will append this path to a base URL. But it seems that the base URL contains the /beta path.
Why? I don’t know, but it seems deliberate. See the help comment in the Make an API call module:
This is not a requirement for Webflow, so I don’t understand the presence of this:
So after some digging, it seems the Webflow App is using v2 beta API: Create Live Collection Item(s) (Data API v2 (beta)) — Webflow API Documentation
I tried it and this works for me, though. So make sure your collection ID is correct.
Cheers,
@Henk-Operative
Hey again and thanks for testing with your own credentials!
My request data is working fine with the playground-tester from webflow but still does not work with make. The URL is relative and formatted as mentioned above. This is what I tested in playground:
I can definitely exclude a wrong collection id. The URL/path in Make also is identical with the one in the playground-tester. I also tried it with the endpoint “create live collection item” as linked by you. This is not working either.
The strange thing is: getting all the items from the collection id with the two cmsLocaleIds via a manual “make an api call” works:
I also checked the app permissions within webflow. Looks totally fine to me:
In my opinion, there has to be a bug with the endpoint “/bulk” - what do you think?
Could be the /bulk path, but in my tests that works. The /bulk can be used to create multiple items for different locales simultaneously. You could try to use the endpoint for single item creation, but once for each locale. (although that is the one I linked)
You probably checked this already, but are you using the correct credentials? Are you able to see the site in which the collection exist if you list the sites? (using: https://api.webflow.com/beta/sites)
Cheers,
Henk
Thanks again, Henk! I tried the single and multiple item creation endpoint.
My credentials are correct, that’s why I can make succesful api calls, e.g. for site infos 
I also checked all collections for the regarding site:
The ID from the first collection called “Immobilien” is the one where I try to create single or multiple items.
What makes it pretty interesting: When I try to create multiple items in another collection, e.g. “Team”.
According to my logic and the tests, there has to be sth. wrong with my collection “immobilien”.
I’ll do some more tests and try to isolate what causes the problems.
Best regards,
Dylan
I finally managed to find and solve the problems:
The field called “referenz” in webflow is an option field and thus needs the according option-id as the value. In my case “e68c93b362dc8abdfb0f5b41dd5a64f8” for “Ja”. The value “Ja” is not supported and causes [404] Route not found. That’s what my first mistake was.
The second problem was my usage of 4 special arrays: webflow does not like the data coming from the onOffice fields “Beschreibung”, “Lage”, “Ausstattung” and “Sonstiges Angaben”, because they contain some special formatting. I had to parse them from html to text. If I did not, it causes [404] Route not found.
That’s it. Now, everything works 
Oh wow, why they chose a 404 error for an invalid payload is strange to me. I was looking for causes within the request itself, not the payload. Great that you figured it out!
Yeah, pretty strange. Thanks a lot for your fast support! What a great community this is
