Hi,
I tried this myself and there are a few problems with your approach.
1. In the first place, you're using the wrong endpoint for the way you're trying to get a response. The async endpoint you are using merely creates the job and returns an ID, which you then need to continue to poll using the Show Jobs asynchronous endpoint, testing the job until it returns as completed. Alternatively, you can use the synchronous "Create Job and Wait" endpoint, which requires only the one request, but you won't be able to make any other API requests while that is running. Either way you decide to do it—a completed job will return a URL, which you will then need to make yet another request for in order to retrieve the file as a blob and save it to Google Drive the way you wish. An alternative to this is possibly to send the parameter "inline" with a boolean value of "true" in the final, export task of the job, which should return the actual file data itself, rather than the URL, although I have not tested this, and it's possible it only works when displaying a converted file directly to a browser. But worth a try to save yet another request.
2. The url you attempt to import from in the first place will need to be publicly shared via Google Drive, i.e. set to "Anyone with the link" in permissions. However, when I tested this, even after setting my test file's permissions in Google Drive to "Anyone with the link", the CloudConvert API job API request failed on the import task with an HTTP error 429, which to me implies Google itself is denying the request, causing CloudConvert to repeatedly try the request, which in turn causes Google to return with HTTP error 429 (too many requests). So it may not be possible to use a Google Drive share link to import from. However, CloudConvert allows import from Google Cloud Storage, and you can manage this with Apps Script (e.g.
https://konfido.github.io/Request-to-Cloud-Storage-API-in-Apps-Script-with-OAuth2/)
3. There is no "folder_id" parameter for the "export/url" endpoint, according to CloudConvert documentation.
4. Make sure that your CloudConvert API key has all necessary scopes for the tasks you are including in your job.
Hope that helps.
Best,
Avana