Resources · Make integration

Melo Make integrationAutomate Melo with Make.

Can Make read your Melo properties and pass them to the rest of your tools? Yes. The Melo Make integration gives you 2 modules: one search and one open API call. This guide is for Melo users who have never built a scenario, and it walks you from the connection to a working test.

Try the Melo integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Melo Make integration?

The Melo Make integration links your Melo account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that searches, acts or passes data along. With Melo you get two bricks, a property search and a call to any endpoint of the Melo API.

Put Melo results in front of the right people. Search Properties pulls the properties that match your criteria, and each one travels through the scenario as a bundle, a single item handed from one module to the next. Add a module from your spreadsheet or messaging app after it and the list lands where your team already works.

Reach what the menu does not show. Make an API Call reuses your Melo connection to hit any endpoint of the Melo API. When the search alone is not enough, this is the module that fills the gap, as long as you know which endpoint you need.

Start from somewhere else. Melo has no trigger in Make, so the scenario opens on a schedule or on a trigger from another app, such as a form. The Make review explains how the editor handles both starts.

What Make does not give you here: the official documentation for Melo is limited, because Make found too little public information about the app. Expect to test each module with Run once before relying on it. If you hit an error along the way, Make troubleshooting covers the usual causes. Melo may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect Melo to Make?

  1. 01

    Add a Melo module

    In a scenario, click the + and search for Melo, then pick Search Properties. In the module panel, click Create a connection. A connection is your Melo account linked to Make once, then reused by both Melo modules.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when you manage several Melo accounts. Then either authorize Make on the Melo page that opens, or paste the key Melo gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. Pick it again in Make an API Call later: there is nothing to reconnect, the same account serves every Melo module in your scenarios.

First scenario

Your first scenario with Melo

GoalWhen the schedule fires, Make searches Melo for matching properties and sends each result to a Melo API endpoint you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. Since Melo has no trigger, the first module will be the search itself, started by the schedule.

  2. 02

    Add Search Properties

    Search for Melo, pick Search Properties and select the connection you created. Fill in the fields the module shows; once connected, Make lists what it can read from your account.

  3. 03

    Chain the API call

    Click the + on the right of the search and add Make an API Call. Map data from the search results into the request, so each property found feeds its own call to the Melo endpoint you target.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received. Open them: if the search returned nothing, adjust your criteria before going further.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on each bundle counts as one operation on your Make plan.

Modules

What the Melo modules do

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

Melo1

Make an API Call

ActionIn the docs only

This module lets you call any endpoint of the Melo API from your scenario, using the connection you already set up. It is your way around the short module list: whatever the API offers, you can reach it here.

When to use it
you need a Melo action that Search Properties does not cover, and you have found the matching endpoint in the Melo API reference.
Watch out
Make documents Melo only partially, so test every request with Run once and read the response bundle before switching the scenario on.
Melo2

Search Properties

SearchIn the docs only

Search Properties hands you the Melo properties that match what you ask for, one bundle per result, ready to be mapped into the next module. It is the natural first step of most Melo scenarios.

When to use it
a colleague needs the current list in a sheet or a chat channel, or another module needs details about each property.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, so narrow your criteria to keep the operation count down.
Need help

Need help automating Melo with Make?

A person reads every message.

FAQ

Melo and Make: common questions

01Is the Melo Make integration free?
Yes. Melo is a standard app in Make, so it is available from the Free plan onward. That plan lets you keep 2 active scenarios, runs scheduled scenarios no more often than every 15 minutes, stops each run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one per module per bundle.
02What do you need to connect Melo to Make?
A Melo account and a Make account. Make's documentation lists no specific prerequisite for Melo. You add a Melo module, click Create a connection, optionally name it, then either authorize Make on the Melo page or paste the key Melo provides, and save. The same connection then serves both Melo modules. Because the documentation is limited, run the first module once to confirm the connection actually reads your data before you build the rest of the scenario.
03Does the Melo module react in real time?
No. Melo has no trigger in Make, neither scheduled nor instant, so nothing fires on its own when something changes in Melo. You start the scenario another way: with Make's schedule on the first module, every 15 minutes by default on a new scenario, or with a trigger from another app placed before Search Properties. Paid plans can shorten the schedule to 1 minute, which brings results closer to the moment they change without making the start instant.
04What if the Melo module you need is missing?
Use Make an API Call. It reaches any endpoint of the Melo API with the connection you already created, so you are not limited to Search Properties. You will need the Melo API reference to know which endpoint and parameters to send. Keep in mind that Make's own documentation for Melo is limited, so testing each call with Run once and reading the returned bundle is the safest way to confirm it behaves as expected.
05Should you use Make or n8n for Melo?
It depends on the tool your team already works in. Melo may also have an n8n node, so you might have two options for the same account. In Make you get 2 modules: Search Properties and Make an API Call, which opens the rest of the API. Compare what each tool offers for Melo against the scenarios you plan to build, and pick the editor your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations