Cannot add custom fields to API calls, will fail validation for instances which require certain data

Open
#3 7 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api

Research direction

Start at the n8n-nodes-cloudinary asset upload node and trace how its Cloudinary API call is assembled. Add support for additional query parameters such as the required client value, then verify that uploads for configurations requiring custom data no longer fail validation.

Written by the indexing model from the issue text.

Description

Hi! Our Cloudinary config requires the client parameter for asset uploads. We get a Field 'client' is mandatory and cannot be left empty error when using the n8n-nodes-cloudinary asset upload node because it currently does not support additional/custom query parameters. We can contribute a PR to make this change, but wanted to ask here first in case this is already planned.

Dominant language
TypeScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/n8n-nodes-cloudinary

All issues in cloudinary/n8n-nodes-cloudinary

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.