Dylan Sather (Pipedream) : ah sorry I forgot to note one thing - you’ll need it to read await fetch…
Mohammed Zeeshan : 2/2
had a check with Postman to confirm the custom field name and format. And it didn’t display any field of that name. Then i manually entered a value to the custom field name. This time when i rerun get request in postman, this field got created, but only for that member.
Mohammed Zeeshan : Added await keyword and retested but it still don’t have return values. Checked postman and it didn’t create those custom fields event though they are specified in Memberstack.
Not sure if i did added the member_id in Line:3 in right way 
Dylan Sather (Pipedream) : It’s subtle but do you see how I wrapped the URL in backticks in my example above? You’ll need to do that to pass the member ID as a variable. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals
Mohammed Zeeshan : Oh i see now 
Dylan Sather (Pipedream) : yes, if you’d like to return the HTTP response, you’ll want something like:
const res = await fetch(...)
// Below your fetch code
return await res.json()
Mohammed Zeeshan : Nvm, i will take a look again tomorrow. It’s 2:40 in the night here
Dylan Sather (Pipedream) : Try removing the JSON.stringify() and just send body: { customFields: { ... } }
Tod Sacerdoti : FYI - I have added the Memberstack app to Pipedream. Due to some issues with Memberstack new user signup I haven’t been able to test with an API key but i believe it is setup correctly. If you have a chance, please test the integration by copying this workflow - Memberstack Integration Test - Pipedream
Mohammed Zeeshan : That didn’t change the error message. I did also try on Postman to get specifics of the error and it says error#422 The request was well-formed but was unable to be followed due to semantic errors.
Mohammed Zeeshan : 
That’s awesome, gonna test now
Mohammed Zeeshan : I have setup that step, connected memberstack and auth key. But i need a help in mapping that auth key to the params property value.
Dylan Sather (Pipedream) : Was there a reason you changed the code step in Tod’s example? You should actually keep it as-is, and once you connect your account, that step will reference your connected account.
Do you receive an error if you use the code Tod provided?
Dylan Sather (Pipedream) : Re: the 422 error, do you see any other details? Feel free to share your workflow (Share button in the top-right) with dylan@pipedream.com
Mohammed Zeeshan : Yeah,following Tod’s example, returned a 401 error, so i thought that would be a placeholder
Dylan Sather (Pipedream) : I see. Could you do me a favor and share that workflow with dylan@pipedream.com, as well?
Mohammed Zeeshan : Yeah sure
Mohammed Zeeshan : Collect, transform & route data in minutes - Pipedream