Molku Zapier integrationAutomate Molku with Zapier.
The Molku Zapier integration gives you 2 triggers, 1 action and 1 search. Enough to send a PDF into a Molku workflow from another app, pick up the filled file when it is ready, and hear about a failed run without checking Molku yourself.
Verified Trustpilot reviews · AI, automation & growth agency
What the Molku Zapier integration actually does
It plugs Molku, which reads data from uploaded files and uses AI to fill PDF templates, into the rest of your tools. You build a Zap (an automation that starts from one event and runs one or more steps after it), and Zapier carries it out every time that event happens.
A workflow started from somewhere else. Run Workflow sends a PDF into one of your Molku workflows. When a document lands in another app with a direct link to the file, the Zap can hand it over without anyone downloading and uploading it again.
A finished file that goes where it is needed. New File Ready fires when a workflow has finished and the output file is ready. The next step can tell someone by email or chat that it is ready; what the trigger sends about the file is something to read in the test.
A warning when a run fails. Workflow Error fires when a run in your account ends with an error, and comes with the error details. Route those to a chat channel and someone can look at the document while it still matters.
What Zapier does not do for Molku. There is one action, and it only starts a workflow: a Zap cannot build or edit a workflow, or change a template. The single search, Get Output File, fetches one generated file by its ID, and only when you already have that ID. And Run Workflow takes a direct link to a PDF only.
If you are still deciding whether Zapier is the right tool, see our Zapier review.
Zapier vocabulary in one minute
Eight words come back all over this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Molku has two: a file ready, a run failed.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like starting a Molku workflow.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked on a timer. Both Molku triggers are instant.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps that follow can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
What it really costs in tasks
Molku is not a premium app, so it works from the free plan. Zapier bills in tasks, and only completed actions count.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Trigger cost0 tasks
- Molku triggersBoth instant, the grid does not apply
Neither trigger costs a task. Each action that succeeds counts once, so a Zap that starts a Molku workflow uses one task per document, and a Zap that then sends an email uses two. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each held to two steps: one trigger, one action. Adding a filter, a search such as Get Output File, or a second action makes it a multi-step Zap, which needs a paid plan. The grid below is how often Zapier checks polling triggers on each plan; it does not apply to Molku, whose two triggers are instant and fire straight away on every plan.
Connect your Molku account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an account on Molku, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Molku
Search for Molku by name in the dialog, select it, then click Add connection. A new tab opens so you can sign in with the account that holds your workflows.
- 03
Grant access
Sign in to Molku in that tab and allow Zapier to use the account. The connection is saved once, then reused by both triggers, the action and the search.
Your first Zap: hear about failed runs in your team chat
GoalEach Molku run that ends with an error and meets your condition posts the error details in your team chat.
- 01
Build: set the trigger
Create a Zap, pick Molku as the starting app and
Workflow Erroras the event, then choose your connection. The trigger is instant, so no interval applies. - 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real one. Read which error details come back.
- 03
Add the filter
Click the plus icon and add Filter. Fill the three boxes: the field to look at, the rule, the value. The filter makes this a multi-step Zap, which needs a paid plan.
- 04
Add the chat action
Add your chat app and its send-message action, pick the channel, then put the error details from the test into the message. Test the step and read what came back.
- 05
Publish
Click Publish to switch the Zap on. Runs that failed before that moment are not reported; only errors from then on reach the channel.
The 2 Molku triggers
2 events start a Zap when something happens in Molku, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New File Ready
Instant triggerIn Zapier“Triggers when a workflow finishes processing and the output file is ready.”
Starts your Zap when a Molku workflow has finished processing and the output file is ready, then passes what Molku sends to the next steps. It is the end of the line for a document Molku has filled.
Workflow Error
Instant triggerIn Zapier“Triggers when a workflow execution in your account finishes with an error. Provides error details.”
Fires when a workflow run in your Molku account finishes with an error, and hands the error details to the steps that follow. It is the only operation of the integration about failures, so it is the one to watch if documents matter to you.
The Molku action
Molku gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Run Workflow
ActionIn Zapier“Starts a specific workflow with a given PDF file URL and name.”
Starts one of your Molku workflows on a PDF, from a link and a name you give it, so the document gets processed without a manual upload.
The Molku search
1 search step looks for data that already exists in Molku, so a later step can use it.
A search step looks up something that already exists and hands it to the steps after it. Molku has one, and three settings decide what happens when the result is not the one you expected.
Get Output File
SearchIn Zapier“Fetches a specific generated file by its file_id”
Fetches one generated file from Molku by its ID, so a later step can send or store that exact file.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there, and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create. Molku offers no find-or-create for Get Output File, so this search only finds.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Molku Zap breaks
Zapier ties no help article to Molku and lists no limit specific to it. What goes wrong is what goes wrong on any Zap.
Three cases to know before you publish. If a Zap misbehaves, see our Zapier troubleshooting guide.
Earlier files and errors never arrive
A Zap only reacts to what happens after you switch it on. Files finished or runs failed before publishing are not picked up; moving that backlog is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your tasks fast.A sudden huge batch
If a trigger suddenly returns a very large batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.
Need help automating Molku with Zapier?
A person reads every message.
