Resources · Make integration

Molku Make integrationAutomate Molku with Make.

Want Molku workflows to start and report back without you clicking around? The Molku Make integration gives you 7 modules: 2 scheduled triggers, 3 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Molku integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Molku Make integration do for you?

The Molku Make integration links your Molku account to Make so a scenario (the automation you build in Make, a chain of modules) can start a Molku workflow, notice when files are processed or a workflow fails, and pass the results to your other tools without writing code.

Kick off Molku from another app. A new row, form entry or email in some other tool can feed Run a Workflow, so the processing starts without anyone opening Molku. List Workflows helps you check which workflows your account can reach before you wire one in.

Deliver the result where people work. Watch Processed Files picks up finished items, Get an Output File fetches what Molku produced, and the next module drops it into storage, a chat or a CRM record.

Hear about failures early. Watch Failed Workflows can post an alert to your team channel, so a broken run gets looked at instead of sitting unnoticed. List Output History lets you look back over past outputs when you need to rebuild a report.

A clear limit: Make's own documentation for Molku is marked as limited, with no official description for any module and no connection guide. Expect to explore the fields in the editor, and keep Make troubleshooting close. For the bigger picture on the platform, read our Make review, and if you are still choosing a tool, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect your Molku account to Make?

  1. 01

    Add a Molku module

    In your scenario, click the +, search for Molku and pick any of its modules. Then click Create a connection. A connection is your Molku account linked to Make once, then reused by every Molku module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the workspace it belongs to. Then either approve Make on the Molku page that opens, or paste the key Molku gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. If the connection works, Make can now read your Molku account, and module fields can offer lists of what it finds there, so you pick instead of typing.

First scenario

Build your first Molku scenario

GoalWhen Molku finishes processing a file, Make fetches the output file and hands it to the next module.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place your first module. Everything you add after that hangs off this starting point.

  2. 02

    Add Watch Processed Files

    Search for Molku, choose Watch Processed Files and select the connection you made earlier. This is a scheduled trigger: Make checks Molku each time the scenario runs.

  3. 03

    Chain Get an Output File

    Click the + on the right of the trigger and add Get an Output File. Map the data coming from the trigger into its fields, so each processed item gets its own output.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles (one item passed from module to module) each step received. Open them to confirm you get the file you expected.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Pick your interval, then flip the scenario on.

Triggers

Molku triggers: what starts your scenario

2 modules start a scenario when something happens in Molku. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Molku as soon as it happens.

Molku1Watch Failed Workflows

Watch Failed Workflows

triggerIn the docs only

Gives you a way to find out about failed Molku workflows without opening Molku yourself. Each failure it picks up becomes a bundle you can route to an alert, a ticket or a log sheet.

How it fires
scheduled, Make checks the app on the scenario's schedule, so a failure shows up at the next check rather than the second it happens.
When to use it
when a failed run blocks someone downstream, such as a document a client is waiting for, and you want the team told in the channel they already read.
Watch out
the documentation gives no description of this module or of what it returns, so run it once on a real failure and read the bundle before you build the alert text.
Molku2Watch Processed Files

Watch Processed Files

triggerIn the docs only

Hands your scenario each file Molku has finished processing, which is the natural starting point for moving results out of Molku and into the tools your team uses every day.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects what was processed since the last check.
When to use it
when a processed file should land somewhere automatically, like a shared folder or a customer record, as soon as the next scheduled check finds it.
Watch out
every file it returns is a bundle, and every module after it spends one operation (one execution Make counts on your plan) per bundle, so a busy account uses operations quickly.
Modules

Everything the Molku app can do in Make

Molku gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Molku1

Get an Output File

ActionIn the docs only

Fetches the file a Molku workflow produced, so the next module can store it, attach it to an email or push it into another app.

When to use it
right after Watch Processed Files or Run a Workflow, once you know which output you need.
Watch out
on the Free plan Make handles files up to 5 MB, so a larger output may need a paid plan.
Molku2

List Output History

SearchIn the docs only

Returns past outputs from your Molku account, so you can review what was produced before or catch up on items a scenario missed.

When to use it
for a one-off backfill, or to build a summary of earlier results in a spreadsheet.
Watch out
as a search it can return zero, one or many bundles, and each one runs the modules that follow it.
Molku3

List Workflows

SearchIn the docs only

Shows which Molku workflows your connection can reach, which is handy when you want to confirm a workflow exists before a scenario calls it.

When to use it
ahead of Run a Workflow, to pick the right one.
Watch out
it is a search, so it can return zero, one or many bundles; run it once and see what comes back before you map anything.
Molku4

Make an API Call

ActionIn the docs only

Lets you reach any endpoint of the Molku API from your scenario, reusing the same connection, when none of the listed modules does what you need.

When to use it
for an operation Molku offers in its API but that has no ready-made module here.
Watch out
you will need Molku's own API documentation, since Make's page on Molku does not describe the endpoints.
Molku5

Run a Workflow

ActionIn the docs only

Starts a Molku workflow from your scenario, so an event in another tool can set Molku to work without anyone pressing a button.

When to use it
when a new form entry, email attachment or record should go straight into Molku for processing.
Watch out
starting the workflow and collecting its result are separate steps, so pair it with Watch Processed Files or Get an Output File.
Need help

Need help automating Molku with Make?

A person reads every message.

FAQ

Molku Make integration: common questions

01Is the Molku Make integration free?
Yes, Molku is a standard app, so it works on the Make Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. This page covers Make only and says nothing about what Molku itself charges.
02What do you need to connect Molku to Make?
A Molku account and a Make account. The documentation for Molku lists no prerequisites and no specific connection steps, so you follow the generic flow: add a Molku module, click Create a connection, optionally name it, authorize Make on the Molku page or paste the key Molku gives you, then click Save. If you are asked for a key and cannot find it, check the settings of your Molku account or contact Molku support. The same connection then serves all 7 modules.
03Does the Molku Make integration react in real time?
No. Judging by their names, since Make's documentation does not describe them, both Molku triggers, Watch Failed Workflows and Watch Processed Files, are scheduled triggers (check the clock badge on the module): Make checks Molku on the scenario's schedule and collects what happened since the previous check. A new scenario checks every 15 minutes by default, and that is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. Neither trigger is instant, meaning Molku does not call Make through a webhook the moment something happens, so plan your alerts with that delay in mind.
04What if the Molku module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Molku API from your scenario with the same connection, so it covers what the 7 listed modules do not. Keep in mind that Make's documentation for Molku is marked as limited: it has no module descriptions and no endpoint details, so you will need Molku's own API reference to know what to call. If Molku cannot do the job at all, another app in Make's catalog of 3,000+ standard apps may cover that step.
05Should you use Make or n8n for Molku?
It depends on the tool you already run. With Make, Molku is available on every plan, including Free, through 7 modules: 2 scheduled triggers, 3 actions and 2 searches, plus Make an API Call for anything else. The same app often has an n8n node too, so check that side if your automations already live in n8n. The honest criterion is where your other workflows are and which editor your team is comfortable in, not a ranking between the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations