Resources · Make integration

MuleSoft Make integrationAutomate MuleSoft with Make.

Can a Make scenario kick off a CloudHub action for you? Yes: the MuleSoft Make integration gives you 2 action modules, one for CloudHub and one for any other API call. This page is for Enterprise plan teams, and it walks you from the connection to a first working scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the MuleSoft integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MuleSoft Make integration let you automate?

The MuleSoft Make integration links your MuleSoft account to Make so that a scenario, the automation you build in Make, can send requests to MuleSoft on its own. You get two modules, the bricks of a scenario: one that triggers a CloudHub action, and one that calls any endpoint of the MuleSoft API with the same connection.

Launch CloudHub from a business event. A record changes in your CRM or a form comes in: Make catches it with that app's trigger, then Trigger a CloudHub Action sends the request to MuleSoft. Nobody has to launch it by hand.

Reach an endpoint the modules skip. When the listed module stops short, Make an API Call reuses your connection to call the MuleSoft API directly. You describe the request, Make handles the authorization.

Chain both in one flow. Trigger the CloudHub action first, then add an API call right after it, so a single scenario covers the whole request. Our Make training shows how to map data between modules.

What Make does not give you here: no trigger. MuleSoft cannot start a scenario by itself, so the first module always comes from another app or from the schedule. The app is also reserved for the Make Enterprise plan. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make review covers the editor itself.

Connect

How do you connect MuleSoft to Make?

  1. 01

    Create a Connected App in MuleSoft

    Log in to MuleSoft, open the left menu and go to Access Management, then Connected Apps and Create app. This app is the door Make will use, so give it a name your team will recognize later.

  2. 02

    Grant the scopes and copy the keys

    Add the scopes the doc lists: API Manager: View APIs Configuration, Runtime Manager: Read Applications, General: View Environment, View Organization, Exchange: Exchange Viewer and OpenID: Profile. Click Save, then Copy ID and Copy Secret, and keep both somewhere safe.

  3. 03

    Paste them into Make

    In Make, open a MuleSoft module and click Create a connection. Type a Connection name, paste the values into Client ID and Client Secret, and click Save. The connection, your MuleSoft account linked once, now serves both modules.

First scenario

Your first scenario with MuleSoft

GoalWhen an event happens in another app, Make triggers a CloudHub action in MuleSoft, then sends a second request to the MuleSoft API for what the CloudHub module does not cover.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your event starts, since MuleSoft has no trigger of its own.

  2. 02

    Add Trigger a CloudHub Action

    Click the + to the right of the first module, search for MuleSoft and choose Trigger a CloudHub Action. Select your connection, then fill the fields; Make lists what it can read once connected.

  3. 03

    Follow up with Make an API Call

    Add one more module: Make an API Call. It reuses the same connection, and you can map data coming from the earlier modules into the request.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, a bundle being one item passed from module to module.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From then on it runs without you.

Modules

What the MuleSoft modules do

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

MuleSoft1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module gives you access to any endpoint of the MuleSoft API, signed with the connection you already created, so you never paste a token by hand.

When to use it
pick it as soon as you need something the CloudHub module does not cover, or to add a second request in the same flow.
Watch out
you write the request yourself, so read the MuleSoft API reference before mapping fields into it.
MuleSoft2

Trigger a CloudHub Action

Action

In Make“Sends a request to Mulesoft to trigger a CloudHub action.”

With this action, your scenario sends MuleSoft the request that sets off a CloudHub action, straight from an event caught in another app.

When to use it
choose it over the generic API call whenever the goal is precisely a CloudHub action: it is the module built for that job, while the generic call leaves the whole request to you.
Watch out
despite its name, it is an action, not a trigger, so the scenario still needs a first module from another app or a schedule.
Need help

Need help automating MuleSoft with Make?

A person reads every message.

FAQ

Questions about the MuleSoft Make integration

01Is the MuleSoft Make integration free?
No. MuleSoft is an enterprise app in Make, and enterprise apps are reserved to the Enterprise plan. The Free plan still exists for the 3,000+ standard apps, with 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, and 5 minutes of execution at most, but it does not open MuleSoft. Paid plans are Core, Pro, Teams and Enterprise, and usage is counted in credits, meaning operations, per month. An operation is one module running on one bundle.
02What do you need to connect MuleSoft to Make?
A MuleSoft account where you can create a Connected App, and a Make account on the Enterprise plan. In MuleSoft, go to Access Management, then Connected Apps, create the app with the scopes the doc lists, save, and copy the ID and the secret. In Make, open the Create a connection window of a MuleSoft module, name the connection and paste the Client ID and Client Secret. The doc lists no other prerequisite.
03Does the MuleSoft Make integration have a real-time trigger?
No, it has no trigger at all, neither scheduled nor instant. Both modules are actions. To start a scenario anyway, place another app's trigger first: an instant trigger, called by that app through a webhook as soon as something happens, or a scheduled one that Make polls. You can also rely on the schedule of the first module, every 15 minutes by default, down to 1 minute on paid plans.
04What if the MuleSoft module you need is missing in Make?
Use Make an API Call. When an app has this module, any endpoint of its API can be called from the scenario with the same connection, so the two listed modules are not a ceiling. You build the request yourself, which asks for a look at the MuleSoft API reference. The only limit the doc gives for this app is the plan: MuleSoft is available on the Make Enterprise plan.
05Make or n8n for MuleSoft?
It depends on your criteria rather than on a winner. On Make, MuleSoft comes with 2 action modules, including a generic API call, and it requires the Enterprise plan. The same app often has an n8n node as well, so compare what each tool offers for your exact MuleSoft tasks and which editor your team already knows. Neither tool is ranked here, and no cost or speed comparison applies. Try one small scenario on each side before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations