Make
Convert a file
Add the HTTP → Make a request module after the module that provides the file (an email attachment, a Google Drive or Dropbox download, a webhook upload) and set:
| Setting | Value |
|---|---|
| URL | https://api.docslice.app/v1/convert |
| Method | POST |
| Headers | Name Authorization, value Bearer <your API key> |
| Body type | Multipart/Form-Data |
Field file |
Type File; map the file's Data and File name from the previous module |
Field format |
Type Text, value json (or markdown, html) |
| Parse response | Yes |
Keep the key in a Make Data store or in the connection settings rather than typing it in several scenarios.
Use the answer
With Parse response on, the fields of the answer appear in the next modules: data holds the converted content (an object for json, text for markdown), document → pages the pages counted. To extract only some fields add a field schema (Text) with your JSON Schema and set format to json; see Schema extraction.
Long documents: asynchronous mode
Create a Webhooks → Custom webhook module and copy its address. In the HTTP module add the fields mode = async and webhook_url = that address. DocSlice answers 202, and when the job ends it sends the result to your scenario as a document.completed event (see Webhooks). Delivery is attempted once, so for important flows also check the job with GET /v1/jobs/{job_id}.
If a request fails
The module reports the HTTP status. 401 means the key is wrong, 402 that the monthly quota is used up and 429 that you sent too many requests: slow the scenario down or add a Sleep step. See Errors and troubleshooting.