Welcome to the official guide for integrating Molku with Zapier. This integration enables you to automate your workflows by connecting Molku's powerful document processing capabilities with thousands of other apps available on Zapier.
Integrating Molku with Zapier enables you to:
<aside> ⚡
Catch us on Zapier and start automating:
https://zapier.com/apps/molku/integrations
</aside>
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 action/trigger and its configuration.
Starts a specific document processing workflow in Molku by providing a direct link to your file, file name and Workflow ID. This action is used to trigger any "Ready to Run" workflow you’ve created in your Molku account. The workflow will process the input file and return either a success or failure status.
You can also pass a file object from a previous step (e.g., from “Google Drive: New File”) in File URL field, which Zapier will automatically hydrate at runtime and convert into a usable file stream:
Input Parameters
| Parameter | Description |
|---|---|
| File URL | 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 also pass the file object from previous step. |
| File Name | The name of the output file. |
| 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. |
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
When you call the Run Workflow action, Molku immediately returns a response indicating whether the workflow was successfully initiated. The document is processed asynchronously, and the final result becomes available shortly after.
Once the workflow has started, you have two ways to handle the output in Zapier:
📌 Option 1: Use a Webhook
If you've configured a webhook, Molku will automatically send the processed file data to that URL when the workflow is complete.
You can handle this using:
📌 Option 2: Use Scheduled Polling in Zapier
If you're not using webhooks, Zapier can poll Molku periodically for updates using the following triggers:
🟢 New File Ready
Triggers when a workflow completes successfully. Returns metadata such as the file name, URL, workflow ID, and credits used.
🔴 Workflow Error
Triggers when a workflow fails. Useful for handling errors or retries in your scenario logic.
This approach lets you monitor workflow results even without setting up webhooks.
Retrieves a specific processed file from Molku using its unique file_id.
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 action/trigger (e.g. webhook). |
Output
Returns metadata and the direct URL to get the generated file.
| --- | --- |
Trigger when a workflow in your Molku account completes successfully and the output file is ready for use.