I would switch over to a JavaScript transform. I highly recommend using AI to write JavaScript code now days. You can do it in the product directly, and I promise we have a better UX coming soon, o...
You just taught me something new! I did not know this was valid JSON, and I was going to say that changing the expected response media to plain text is the correct solution, but now that is not acc...
I def missed that point. Let me ask some questions to better understand this. Can you share the full HTTP response so we can see what it looks like? I am curious if we are getting back a JSON paylo...
The reason the fields are mandatory is because you are setting "Error values" and "Success value". These fields are dependent on the fields above them being set. If you unset these fields, then the...
Can you share a screenshot? i.e. I just checked, and I am not seeing these fields as required in my account.
Hey Dave Guderian, the pre-built flow step that you picked from the marketplace is for transferring raw/blob files that were first retrieved via a 'transfer' flow step in your flow. Following is a ...
Anytime you change scopes in Zoom's admin backend, you need to edit the connection resource in Celigo again, and click on the 'Save & authorize' button. And then when you go back through the oauth2...
I recently built a flow for Zoom, and whenever I got similar scope errors, I had to go into Zoom's admin center and update the scopes accordingly. Go here. https://marketplace.zoom.us/user/build ...
The "Failed to locate headers in the configured sheet." issue should be fixed now. This was a bug on our side.
[updated] -- I know what the issue is. Stay tuned. Ignore this. It would be good to get confirmation that the sheet name being configured matches what it in the spreadsheet. I see the name of the s...