Resources · Make integration

XMP Make integrationAutomate XMP with Make.

Need XMP inside a Make scenario without setting up any account? The XMP Make integration gives you 1 action module, called Actions, and it works without a connection. This page shows where it fits, how to add it and how to test your first scenario.

Try the XMP integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the XMP Make integration do?

The XMP Make integration is a built-in app of Make with a single action module, Actions. A scenario (the automation you build in Make, a chain of modules) can call it on any bundle it receives, and you never have to link an account first.

A module is one brick of a scenario, and an action module works on one item at a time. Make calls that item a bundle: one file, one contact, one row passed from the previous module. Since XMP has no trigger, something else has to start the flow, and then Actions does its job on each bundle that comes through.

The first way to start it is to put a trigger from another app in front. That app watches for its own event, hands over the data, and Actions takes the next slot. If you want to see how other apps behave as the first brick, the 123FormBuilder Make integration is a good example of an app that feeds a scenario.

The second way is to let Make run the scenario on a schedule. A new scenario checks every 15 minutes by default, and the clock on the first module lets you change that. The third way is manual: click Run once while you build, which also shows you exactly what Actions received.

Know the limits before you start. Make documents a single module for XMP, with no official description of what it does, so the page stays on how to place and test it. There is no Make an API Call module for this app either. If you are comparing tools, read n8n vs Make, and if a scenario keeps failing, Make troubleshooting covers the usual causes.

Connect

How do you set up XMP in Make?

  1. 01

    Add the XMP module

    Open your scenario, click the + where the next brick should go, type XMP in the search box and pick the Actions module. It appears in the flow right after the module that feeds it.

  2. 02

    Skip the connection

    With most apps, Make asks you to click Create a connection to link your account. XMP is different: the documentation says you do not need to establish a connection, so there is no key to paste and no authorization window.

  3. 03

    Fill in the fields

    Fill in what the module asks for, mapping values from the previous module where they fit. Your setup is then ready for the first test with Run once.

First scenario

Your first scenario with XMP

GoalWhen another app hands a bundle to the scenario, Make passes it to the XMP Actions module.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that should start the flow, since XMP has no trigger of its own.

  2. 02

    Set up the starting module

    Configure that first module and its connection. Once it is linked, Make lists the folders, sheets or objects it can read, so you choose them from a menu instead of typing names.

  3. 03

    Add XMP Actions

    Click the + on the right of the first module, search for XMP and pick Actions. No connection is needed. Map the data coming from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Read what Actions received to check that the right data reached it.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, keep in mind you get 2 active scenarios.

Modules

What the XMP module can do

XMP gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

XMP1

Actions

ActionIn the docs only

Actions is where XMP does its work in a scenario: it takes the bundle handed over by the previous module and runs on that single item. Each run counts as an operation, the unit Make tracks on your plan.

When to use it
right after the module that produces the data you want XMP to handle, so every bundle goes through it.
Watch out
Make publishes no description of this module, so test it with Run once and read its output before you rely on it.
Need help

Need help automating XMP with Make?

A person reads every message.

FAQ

XMP and Make: common questions

01Is the XMP Make integration free?
Yes. XMP is a standard app, so you can use it from the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every plan counts usage in operations, one per module run on one bundle, so Actions uses one operation each time it handles an item.
02What do you need to connect XMP to Make?
Nothing beyond a Make account. The XMP documentation states that you do not need to establish a connection to use the app, and it lists no prerequisites. So there is no API key, no login page and no authorization step. You add the Actions module to a scenario and fill in its fields. The only accounts you will link are those of the other apps in the same scenario, for example the one whose trigger starts the flow. Each of those connections is created once and then reused by every module of that app.
03Does XMP react in real time in Make?
No, because XMP has no trigger at all, neither scheduled nor instant. Its only module is an action, so the scenario has to start somewhere else. You have three options. Put an instant trigger from another app first, and the scenario runs as soon as that app calls Make. Put a scheduled trigger from another app, and Make checks it on the schedule you set. Or run the scenario on a schedule of its own, every 15 minutes by default and 1 minute at best on a paid plan. Actions then runs on each bundle it receives.
04What if the XMP module in Make is not enough?
It depends on what you need. XMP offers a single module, Actions, and unlike many apps it has no Make an API Call module, so you cannot send custom requests through it. Start by testing Actions with Run once and reading its output, since Make gives no official description of it. If it still does not cover your case, look for another app in Make that handles the same task, or ask the Hack'celeration team, which can look at your scenario and suggest a workaround built with modules you already have.
05Should you use Make or n8n for XMP?
It depends on which tool you already use. On the Make side, XMP is a built-in app with one action module, no connection to create and access from the Free plan, which keeps the setup very short. On the n8n side, many apps have their own node, so check whether one exists for what you want to do before you choose. The honest criterion is the tool your team already runs and maintains. Rebuilding a working scenario in another tool only makes sense if the module you need exists there and not here.
Same platform

Other docs you might need on this stack.

Browse all integrations