Resources · Make integration

MusicGPT Make integrationAutomate MusicGPT with Make.

Can MusicGPT turn a request from another tool into a queued music task on its own? The MusicGPT Make integration gives you 3 action modules and no trigger. This guide is for teams that already use MusicGPT: it connects your API key and walks you through a first scenario.

Try the MusicGPT integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MusicGPT Make integration do for you?

The MusicGPT Make integration links your MusicGPT account to Make so a scenario (the automation you build, a chain of steps) can queue a music generation task and look up a task by its ID. Each step is a module, one brick of the scenario. MusicGPT has no trigger, so the scenario starts from another app or from a schedule.

Status lookups without opening MusicGPT. When you already hold a task ID, Get conversion/task details by ID pulls the details of that task into the scenario, where later modules can write them to a sheet or a message.

Music requests from your other tools. A form, a spreadsheet row or a support ticket from another app can start the scenario, and Queue a music generation task sends the request to MusicGPT with the data mapped from that first module.

Anything else the API offers. Make an API Call reaches any endpoint of the MusicGPT API with the same connection, which covers what the two dedicated modules leave out.

Keep one limit in mind: the Make documentation for MusicGPT says it was generated by AI from the vendor documentation and may contain mistakes, so check anything important with MusicGPT. If you are still weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted. To learn the editor step by step, see the Make training.

Connect

How do you connect MusicGPT to Make?

  1. 01

    Create an API key in MusicGPT

    Open the API dashboard of your MusicGPT account, go to API Keys, click Create key, name it, then Create API Key. Click the Eye symbol to reveal the key and copy it.

  2. 02

    Add a MusicGPT module

    In your Make scenario, add any MusicGPT module and click Create a connection. A connection is your MusicGPT account linked to Make once, then reused by every MusicGPT module.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you want (it is optional), paste the API key you copied, and follow the on-screen instructions to finish the connection.

First scenario

Your first scenario with MusicGPT

GoalWhen a new request lands in another app, Make queues a MusicGPT music generation task and then reads the details of that task.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. MusicGPT has no trigger, so this first module comes from the app where your requests live.

  2. 02

    Add Queue a music generation task

    Click the + to the right of that module, search for MusicGPT and pick Queue a music generation task. Link your account with Create a connection, then map the request data from the first module.

  3. 03

    Add the status lookup

    Add Get conversion/task details by ID after it. If the bundle returned by the queue module carries a task ID, map it here; a bundle is one item passed from one module to the next.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and confirm the ID really reached the lookup module.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What the MusicGPT modules do

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

MusicGPT1

Get conversion/task details by ID

ActionIn the docs only

This module fetches the details MusicGPT holds for one conversion or task, from the ID you give it, and passes them on as a bundle for the next modules to use.

When to use it
after a task was queued earlier, to find out where it stands and send the result to a sheet, a chat channel or a customer record.
Watch out
it works on one ID at a time, so the ID must come from a previous module or from a value you stored earlier.
MusicGPT2

Make an API Call

ActionIn the docs only

With it you reach any endpoint of the MusicGPT API from your scenario, reusing the connection you already created instead of setting up authentication again.

When to use it
when the two dedicated modules do not cover what you need from MusicGPT, for example an endpoint that has no module of its own in Make.
Watch out
you write the request yourself, so keep the MusicGPT API documentation open and test the call with Run once before switching the scenario on.
MusicGPT3

Queue a music generation task

ActionIn the docs only

Here is the module that puts your request into MusicGPT: it sends a music generation task to the queue from the data you map, for example a request captured by another app.

When to use it
as the action right after the module that collects a new request, such as a form entry or a new row in a spreadsheet.
Watch out
the name says the task is queued, so plan a later lookup with Get conversion/task details by ID rather than expecting the finished track in the same step.
Need help

Need help automating MusicGPT with Make?

A person reads every message.

FAQ

MusicGPT and Make: common questions

01Is the MusicGPT Make integration free?
Yes, on the Make side. MusicGPT is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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. Your MusicGPT account and its API access are a separate matter: the documentation points to the MusicGPT pricing page for the subscription.
02What do you need to connect MusicGPT to Make?
You need an active MusicGPT account and an API key. The key is created in the API dashboard of MusicGPT: open API Keys, click Create key, give it a name, confirm with Create API Key, then reveal it with the Eye symbol and copy it. In Make, add a MusicGPT module, click Create a connection, optionally fill in Connection name, and paste the key. That connection is then reused by every MusicGPT module in your scenarios, so you only do it once.
03Does the MusicGPT integration react in real time?
No. MusicGPT has no trigger in Make, neither scheduled nor instant, so nothing in MusicGPT can start a scenario by itself. You start it another way: with the trigger of another app, such as a new form entry, or with the schedule on the first module, which runs every 15 minutes by default on a new scenario. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs; paid plans go down to 1 minute.
04What if a MusicGPT module is missing in Make?
Use Make an API Call. MusicGPT has this module, and it lets a scenario call any endpoint of the MusicGPT API with the same connection as the other modules. That covers what the queue and lookup modules do not. Before relying on a detail, remember that the Make documentation for MusicGPT states it was generated by AI from the vendor documentation and may contain mistakes; for important points, check with MusicGPT directly and test every call with Run once.
05Should you use Make or n8n for MusicGPT?
It depends on the tool your team already runs. On Make, MusicGPT offers 3 modules, available from the Free plan, plus Make an API Call for the rest of the API, and the scenario is built visually with a Run once test. Many apps also have an n8n node, so check whether MusicGPT has one before choosing. The comparison between the two tools is about criteria, not a ranking: pick the platform where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations