Howto set up HTTP POST request with Coda.io data

Hi, I’m new to using Make. Just started yesterday. I’ve gone through the Intro to HTTP Academy course. However, since I’m so new, it’s hard to know how to search for the help I need. After spending some hours reading through documentation and watching videos, I’m still not sure how to get this to work.

I have a scenario that gets Row data from a table in Coda.io. I believe the data that comes from Coda is JSON formatted.

Next I added a JSON module to Create JSON from the Coda module. It seems like without that, then HTTP module doesn’t see the data from the Coda module. Or if it does, I can’t figure out how to work with it. Which is my next issue.

I have the HTTP module next:

I am sending the data to an app called Que which allows me to automate video creation in Adobe After Effects. Here is where I’m not sure what to do next. I have body type set to Raw, and content type set to JSON, which is what Que requires. Now, I’m not sure how to assign specific data when sending it to Que. I figure something has to go into the Request Content field, but I’m not sure what.

I know that’s a lot, but if anyone can help, or point me in the direction of some documentation or videos that would explain this, I’d appreciate it.

Thanks,
Lee

Welcome to Make!

For Coda, you should be able to access the response values directly, and then you can “map” it in the next modules. If you really don’t manage to map any value from the coda module, running the scenario at least once may help. After one run, the values should be visible.

Then, for Que, you need to follow their API documentation to figure out what data should be entered in the request content field.

So in that case the request content should probably look like this:

2 Likes

Thank you for that last image, Thomas. I think what confuses me is that in some situations, there are individual fields that the data can be mapped to. And in others, like this one, it’s just one field for “requested content” that I have to figure out how to format it myself. But it looks like that’s how I have to do it. I will work on that and reply back if it works out or if I have other questions. Thanks for your response!

I changed my Request content to this:

Now I’m getting a 500 Internal Server Error after running the scenario.

When I download the Input Bundle, I get this:
[
{
“ca”: null,
“qs”: ,
“url”: “https://que-api.dataclay.com/api/v1/jobs/”,
“data”: “{\n\t"projectId" : "64bfe1fbe8c487a41fce7879",\n\t"Frog_1" : "DPOS1",\n\t"Frog_2" : "Really just the things above.",\n "Frog_3" : "Really just the things above.",\n "Date_Submitted : "2023-08-02T00:00:00.000-04:00",\n "Created_By" : "Lee Legg"\n}”,
“gzip”: true,
“method”: “post”,
“headers”: [
{
“name”: “Authorization”,
“value”: “Bearer 2c6499f1eec499cbf8681b4d649ea9acb101a74f4cfea01847497346e2fe9f2b7e9b264c0cb72716f1b16cf7c262e150”
}
],
“timeout”: null,
“useMtls”: false,
“authPass”: null,
“authUser”: null,
“bodyType”: “raw”,
“contentType”: “application/json”,
“serializeUrl”: false,
“shareCookies”: false,
“parseResponse”: false,
“followRedirect”: true,
“useQuerystring”: false,
“followAllRedirects”: false,
“rejectUnauthorized”: true
}
]

Why does the “data” info get reformatted from what I input in the Request Content field? I don’t know if that’s what’s causing the error, but I don’t get an error if I leave the Request Content field empty. I’m also working with Que’s support to see if they can understand it.

I was really hoping I could get this to work with Make, but I may have to go back to Zapier. It costs more, and I prefer Make’s UI, but if Make won’t work, I’ll just have to go back, at least for now.

In fact the \n and \t that you see just represent the spacing or tabulation. So if you remove all the spaces from your request content, these characters should disappear.

2 Likes

I’m still getting a 500 Internal server error. I’ve checked with the Que team, and they want me to use Postman to make sure I’m able to send data. So now I have to learn something else. Thanks for your help Thomas.

1 Like