Make is a visual automation platform that allows you to connect Molku with thousands of other apps to build custom document workflows. With Molku and Make, you can automate the transformation of files—parsing data from one format and generating new, structured PDF documents based on your workflow configuration.
Integrating Molku with Make enables you to:
<aside> ⚡
Catch us on Make and start automating:
https://www.make.com/en/integrations/molku
</aside>
Create a connection dialog.
Once connected, you can start building scenarios using Molku triggers (e.g. workflow completion) and actions (e.g. run a workflow, retrieve output data).
In the following sections, we’ll guide you through each available module and its configuration.
This action allows you to trigger a document parsing process based on a workflow you’ve created and marked as "Ready to Run" in the Molku interface. The workflow will process the input PDF and return either a success or failure status.
Input Parameters
| Parameter | Description |
|---|---|
| Workflow ID | The unique ID of the workflow to run. Must reference a workflow that is set to "Ready to Run" status. You can select a workflow from the dropdown list or enter the ID manually. |
| File URL or Base64 | A direct URL to the file that will be processed by the workflow. The link must point directly to the file (i.e. it should open/download the file without redirects or authentication). You can pass the link as a text value from a previous module, or use the result of using “HTTP -> Get a file” and convert the buffered data to a base64-encoded string using the following format: |
| data:{{mimeType}};base64,{{base64(data)}} | |
| File Name | The name of the output file. |
Example (base64 format):
Upon calling the Run Workflow action, Molku returns an immediate response indicating whether the workflow has started successfully. The actual processing is asynchronous and continues in the background.
Output & Result Handling
After initiating the workflow via the Run Workflow action, Molku responds immediately with a workflow_status: "started". The actual processing happens asynchronously.
To handle the final result, you have two options:
📌 Option 1: Use Webhooks (Recommended for real-time workflows)
If you configured a webhook, Molku will send a callback once the workflow is complete. This can be handled in Make using the Custom webhook module to trigger downstream steps dynamically.
📌 Option 2: Use Polling Triggers in Make
Molku also provides two dedicated trigger modules to help you monitor workflow completion over time:
🟢 Watch Processed Files
Triggers when a workflow completes successfully. Returns metadata including file name, workflow ID, and credits used.
🔴 Watch Failed Workflows
Triggers when a workflow fails. Useful for handling errors or retries in your scenario logic.
These modules allow you to periodically check for completed or failed workflows without setting up webhooks.
Use this action to retrieve the final PDF file and associated information (e.g. name, status, credits used) after a workflow has finished processing.
Input Parameters
| Parameter | Description |
|---|---|
| File ID | The unique ID of the file you want to retrieve. You can select a file_id from the dropdown, or enter it dynamically from an earlier module (e.g. webhook or get output history module). |
Output
Returns metadata and the direct URL to get the generated file.
| Parameter | Description |
|---|---|
| ID | Unique file ID. |
| File Name | Name of the output file. |
| URL | Direct link to the generated PDF. |
| Status | Processing status (Success or Error). |
| Is Public? | Indicates whether the file is publicly accessible. |
| Workflow ID | ID of the workflow that produced this file. |
| Used Credits | Number of credits consumed for processing. |
| Date Created | Timestamp (in milliseconds). |
Returns a list of output files generated from completed workflows in your Molku account. Use this module to retrieve recent workflow results, including metadata such as file id, creation date, and status.
Output
The module returns a bundle of records, each representing an output file generated by a completed workflow.
| --- | --- |