Why am I Receiving a 400 Error when Updating a CMS Item using Webflow's API?

Help
21

Is Pipedream creating the API call wrong

22

Yes, that’s what I believe is going on:

https://github.com/PipedreamHQ/pipedream/blob/1506cff1d9280a64c322a125384404e24f4e[…]bflow/actions/update-collection-item/update-collection-item.mjs

All of our components including this Webflow - Update Subscription Item are open source.

I believe that specific line I linked to is passing the custom fields at the top level of the API request to WebFlow, but in fact they need to be passed as a nested object under the fieldData key.

23

I’m opening a bug report for our component developers to confirm this is a bug.

24

I’ve opened a bug report here: [BUG] `customFields` not mapped correctly for Webflow's Update Collection Item action · Issue #9257 · PipedreamHQ/pipedream · GitHub

And it’s prioritized for our team to review and fix. Please subscribe to this issue for updates.

But in the meantime you can still use Node.js or Python or even the HTTP Request builder action to make this request to Webflow and bypass this bug in the pre-built action.

25

Thank you very much Pierce, that’s great

26

Happy to help. Hopefully this bug is solved relatively quickly. It seems like a minor change.

27

Hi Iarla, just a notice the bugfix has passed testing:

It should be merged shortly, when it is you’ll see an Upgrade Component button in the top right of the step that allows you to update it to this latest version.

28

Perfect, that’s working now. Thanks very much again