Is it possible to use a Dictionary input field for custom fields?

Hi @ikbelkirasan 
I’m really sorry for the trouble, but it’s still throwing me an error when testing the Zap. 
This is my code when Configuring the API Request:

And this is the error being thrown in the Zap:

The API requires a string value so I used JSON.Stringify. but in the Zap it doesn’t seem to register the JSON.stringify method and seems to still be throwing an object. 

Am I doing this wrong? 

Again, I am very thankful for your advice. 

@ikbelkirasan I see, this is the current code that I have:

  params: {
    'apiKey': bundle.authData.apiKey,
    'subdomain': bundle.inputData.subdomain,
    'studentId': bundle.inputData.studentId,
    'customFields': JSON.stringify(bundle.inputData.customFields)
  },
  body: {

  }
};

return z.request(options)
  .then((response) => {
    response.throwForStatus();
    const results = response.json;

    const payload = Object.entries(bundle.inputData.customFields).map(([key, value]) => `${key}: ${value}`);

    return results;
  });

So, it should be like this, is this correct? 

  params: {
    'apiKey': bundle.authData.apiKey,
    'subdomain': bundle.inputData.subdomain,
    'studentId': bundle.inputData.studentId,
    'customFields': JSON.stringify(bundle.inputData.customFields)
  },
  body: {

  }
};

   const payload = Object.entries(bundle.inputData.customFields).map(([key, value]) => `${key}: ${value}`);

return z.request(options)
  .then((response) => {
    response.throwForStatus();
    const results = response.json;


    return results;
  });

That worked. Thank you so much! 

Just a quick question though, does that mean when I set a value as JSON.stringify() in the parameters, this won’t register for the zap? because I noticed that this happens for the fields that I add the JSON.stringify method too. 

It’s just a bit confusing when in the developer mode testing the api works but when I test it in the zap it throws an error. 

@ikbelkirasan I checked the monitoring, and in the development, the values being sent are correct

But in the Zap, it ends up sending the values in a different format

Why is it that the Zap isn’t sending the values the same way as when testing from the developer mode? 

@ikbelkirasan 

This is the api configuration in the developer mode

const options = {
  url: 'https://...',
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Accept': 'application/json',
    'X-API-KEY': bundle.authData.apiKey
  },
  params: {
    'apiKey': bundle.authData.apiKey,
    'subdomain': bundle.inputData.subdomain,
    'studentId': bundle.inputData.studentId,
    'customFields': JSON.stringify(bundle.inputData.customFields),
    'fields': 'customFields'
  },
  body: {

  }
}

return z.request(options)
  .then((response) => {
    response.throwForStatus();
    const results = response.json;

    // You can do any parsing you need for results here before returning them

    return results;
  });

This is the test data in developer mode:

This is the Action Setup in the Zap:

When I test the Zap, it shows as successful, but the data being sent is in a different format, so our API doesn’t handle it the way it’s supposed to. 

The Input field for the Custom Fields is set to a String.

Should I change the field type to a Text instead? In order for the values to be sent correctly?

Again, I apologize for the bother, since I’m new with Zapier I’m a bit confused as to why this is happening.

@ikbelkirasan I see, would the Dictionary field word for fields (example: studentIds) that requires this value: [“1234”, “234”] as well? 
Since I have other actions with the same issue that I JSON.stringify for, but similar to the one above, that instead of this being sent as [“123”, “456”], the zap ends up sending it as “123, 456”.

I hope that explanation was understandable.