Problem with Webflow Update Collection Item API

I am trying to use the Webflow Update collection item API. The connector does not allow me to add more fields beyond name and slug and seems to be missing some of the other fields in the API call. I need to be able to update fields beyond the name and slug, and i am able to send the API request if I use the Webflow interface

Hi @christina.stejskalova,

I understand that you’re trying to update more fields than just the name and slug using the Webflow Update Collection Item action in Pipedream. To do this, you can follow these steps:

  1. Search for the Webflow app from the step menu in your Pipedream workflow.
  2. Select the Update Collection Item action.
  3. Connect your Webflow account.
  4. Select a Site or pass a string from a previous step.
  5. Select a Collection or pass a string from a previous step.
  6. Select an Item or pass a string from a previous step.
  7. Select a Name or pass a string from a previous step.
  8. Select a Slug or pass a string from a previous step.

After completing these steps, you can add more fields to the action by clicking the “+” button at the bottom of the action configuration. This will allow you to add more fields to the API call.

If you still face issues or need further assistance, please visit https://pipedream.com/support for more support options.
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double check my answers and code! Learn how to build your own.

Hi @christina.stejskalova,

From Webflow API doc here, I can see they allow to update name, slug, _archived, and _draft.

May I ask what specific field you’d like to update?

Hmm, I am able to do it via the webflow API too. What I am saying is that I cannot add fields beyond name and slug in the pipedream interface for thw webflow API.

Those were the 2 screenshots. The first showed the webflow api and then the pipedrean interface

Hi @christina.stejskalova,

Pipedream Webflow action is using the same Webflow API. To improve Pipedream Webflow action, I first need to understand your needs (.e.g the sepecific fields you want to use aside from name and slug) so I can create a ticket for it

Yep. That makes sense, what I am trying to say is that I don’t see the options to add any fields beyond name and slug:

_archived
_deleted
And then of course I have a custom field called image_url. So what I am looking for is the ability to add and extra field to the pipeldream UI. If you look back at this task, I attached 2 screenshots in the beginning. One with the webflow API UI(the same as the one you attached) and the second with what I see in pipedream. There you can see that if you put in the name and slug of your collection, I cannot add additonal fields. The fields tab in the webflow api.

Hi @christina.stejskalova, so image_url is a custom field in your collection’s definition?
For custom fields, we have a pending feature being tracked here: [FEATURE] Evaluate custom expression in async options & additionalProps · Issue #3255 · PipedreamHQ/pipedream · GitHub.
This feature will enable actions and sources to be able to dynamically load custom attributes (using additionalProps) for any entity when using custom expressions (e.g. a dynamic id in your workflow).

@vunguyenhung for now, to be able to support @christina.stejskalova’s request we can create a issue request for an object prop where the customer can input desired key / values for their collection, what do you think?

Thanks @andrewcturing, @christina.stejskalova,

I have created a ticket here: [FEATURE] Webflow Update Collection Item action - Add Custom Fields prop · Issue #6579 · PipedreamHQ/pipedream · GitHub. Kindly subscribe to the ticket to be noticed when this is shipped

Awesome thank you both!

FWIW I found a workaround by just directly writing out the api in your other webhook/http request module.

The problem with that one is that it doesn’t allow you to add path parameters into the URL api. I can make another feature request for that.

Best,
Christina

@christina.stejskalova are you talking about this HTTP action? You can modify the URL however you want – or am I misunderstanding what isn’t working for you?

That’s the one. Can you show me how to add path parameters to the api url?

For example in your example you have the url :

Api/webflow.com/info.

But if I want to call a collection I would have

Api/webflow.com/info/{campaign_id}

Per webflows api docs
I tried to put the parameters in the parameters section but it failed. Looking at postman, they have an additional tab call path where you can add path parameters like campaign ID to the UrL

If there is a different way of doing this would love to know

Oh, you can just modify that text input like below. For example I referenced a step that you might have, get_campaign_id, but depending on where the ID is coming from, you can update that reference accordingly. Does that make sense?

Hmm almost, what about if I am not getting the ID from pipedream steps?

You can enter whatever you want in that input field. Where is the campaign ID coming from? Is it a static value? If so, you can enter a static URL in that field. Otherwise if it’ll change and you need to update the ID every time your workflow runs, you’d want to reference it dynamically, like in my example.