Resources · Make integration

Magic Eden Make integrationAutomate Magic Eden with Make.

Need Magic Eden data in your other tools without copying it by hand? The Magic Eden Make integration gives you 16 modules, all actions that read wallets, tokens, collections and offers. This guide links your account, builds a first scenario and shows when each module fits.

Try the Magic Eden integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Magic Eden Make integration do for you?

The Magic Eden Make integration lets a Make scenario (the automation you build, a chain of modules) read data from Magic Eden and pass it to your other apps. Each module is one brick of that chain. Here, every module is an action that fetches something: a wallet's tokens, a collection's statistics, the offers on a token.

A holdings sheet that stays current. Get a Wallet's Tokens fills a spreadsheet with what a shared wallet holds, and Get a Token's Metadata adds readable details to each line, so nobody has to rebuild the inventory by hand.

Offer alerts where the team already talks. Get Offers Received by a Wallet hands each incoming bid to a message module in your chat app.

A collection watchlist. Get a List of Collections, followed by Get a Collection's Statistics, writes one row per collection each time the scenario runs. Every module run is an operation, the unit Make counts on your plan, and the Make pricing page helps you estimate what a watchlist uses.

What Make does not do here: Magic Eden has no trigger, so nothing starts by itself when a sale happens, and Make's own documentation says its coverage of this app is limited. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training covers scenario basics step by step.

Connect

How do you connect Magic Eden to Make?

  1. 01

    Add a Magic Eden module

    In any scenario, add a Magic Eden module and click Create a connection. A connection is your Magic Eden access linked to Make once, then reused by every Magic Eden module you add later.

  2. 02

    Name the connection

    Give it a name if you want, such as the team or the wallet it serves. This step is optional, yet it saves confusion the day you keep several connections side by side.

  3. 03

    Authorize and save

    Authorize Make on the Magic Eden page if one opens, or paste the key Magic Eden gives you, then click Save. The module can now read data through that connection.

First scenario

Build your first scenario with Magic Eden

GoalWhen a new wallet arrives from another app, Make reads what Magic Eden knows about it and lists the tokens it holds.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. Since Magic Eden has no trigger, this first bubble will hold another app.

  2. 02

    Start from the app that receives wallets

    Search for the app where wallets land, a form or a spreadsheet for instance, and pick its module. That app decides when the scenario starts and passes each wallet along as a bundle, one item at a time.

  3. 03

    Add Get a Wallet's Information

    Click the + on the right, search for Magic Eden, choose Get a Wallet's Information and click Create a connection. Then map the wallet from the first module instead of typing it.

  4. 04

    Chain Get a Wallet's Tokens

    Add one more module with the +, pick Get a Wallet's Tokens, reuse the same connection and map the same wallet. You now read the profile and the holdings in a single pass.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time, then open each bubble to read the bundles it received. If a result comes back empty, check the mapped wallet first.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From then on, each new wallet flows through both Magic Eden modules without you.

Modules

What each Magic Eden module does

Magic Eden gives you 16 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Magic Eden1

Get Offers Made by a Wallet

ActionIn the docs only

Pulls the offers one wallet has placed, so you see what a buyer is bidding on without opening Magic Eden. The results reach the next module ready to be mapped.

When to use it
you follow a collector account and want its open bids logged in a sheet each time the scenario runs.
Watch out
Make documents no fields for this app, so open the module to see what it asks for before planning the rest.
Magic Eden2

Get Offers Received by a Wallet

ActionIn the docs only

Shows the other side of the market: the offers other people have sent to one wallet. You get them ready to be sent to a chat or stored further down the scenario.

When to use it
a team shares a wallet and wants every incoming bid surfaced where it already talks, instead of someone checking the marketplace.
Watch out
an action has no clock of its own, so a scenario built on it only sees new offers when its schedule fires.
Magic Eden3

Get Received Offers for a Token

ActionIn the docs only

Narrows the view to a single token and returns the offers it has received, handy when one item matters more than the whole wallet.

When to use it
pick it over Get Offers Received by a Wallet when you only care about one item you plan to sell.
Watch out
if several offers come back as separate bundles, every module after it runs once per offer and uses more operations.
Magic Eden4

Get a Collection's Activities

ActionIn the docs only

Retrieves what has been happening in a collection, the activity feed you would otherwise scroll through on the marketplace, and hands it over for storing or comparing.

When to use it
a community manager wants a running record of a collection's movement in a spreadsheet to spot the busy moments after a drop.
Watch out
Make does not say which activity types or how many entries one call returns, so read the output of a test first.
Magic Eden5

Get a Collection's Listings

ActionIn the docs only

Returns the items currently listed for sale in one collection, which gives your scenario the supply side of the market in a form it can sort.

When to use it
choose it when the question is what can be bought now, rather than what already happened, which is the job of Get a Collection's Activities.
Watch out
a listing can vanish between two runs, so treat the result as a snapshot taken when the module ran.
Magic Eden6

Get a Collection's Statistics

ActionIn the docs only

Gives you a collection's figures in one go, the kind of summary you glance at before deciding whether a collection deserves attention.

When to use it
a small analyst desk wants the same summary written to a new row on every scenario run, so a chart built on that sheet shows the trend.
Watch out
Make's page does not list which statistics come back, so check the bundle after a test before you map any column.
Magic Eden7

Get a List of Collections

ActionIn the docs only

Brings back a list of collections from Magic Eden, a starting point when you do not know yet which collection to follow.

When to use it
place it early in a scenario that feeds each collection into Get a Collection's Statistics, to build a watchlist instead of typing names by hand.
Watch out
a list turns into many bundles, and each module after it counts one operation per bundle, which adds up on your plan.
Magic Eden8

Get a List of Launchpad Collections

ActionIn the docs only

Lists the collections shown in the Magic Eden Launchpad, so you can pass them to a sheet or a chat without checking the page yourself.

When to use it
a community team shares launchpad projects with its members and wants the list pulled into a message draft before posting.
Watch out
Make does not document how this list is sorted or filtered, so compare the output with the Launchpad page on your first test.
Magic Eden9

Get a Token's Activities

ActionIn the docs only

Traces the history of one token, what happened to it on the marketplace, and returns it in a shape your scenario can file.

When to use it
pick it instead of Get a Collection's Activities when a single item is under review, for example before answering a buyer about a disputed sale.
Watch out
map the token from an earlier module rather than pasting it, or the scenario stays stuck on the same item.
Magic Eden10

Get a Token's Listings

ActionIn the docs only

Checks how one token is listed on Magic Eden, a quick way to confirm an item is still on sale before you tell anyone it is available.

When to use it
a seller tracks a handful of items and wants a sheet to show which ones are still listed after changing a price.
Watch out
feed it several tokens and it runs once per token, so keep the list short while you test.
Magic Eden11

Get a Token's Metadata

ActionIn the docs only

Fetches the descriptive data of a token, the information that makes an item recognizable, so a message or a record shows more than a raw identifier.

When to use it
add it after Get a Wallet's Tokens when a report needs readable details for each item rather than codes.
Watch out
with no field list in the doc, the mapping panel is where you discover what comes back; build the next module after a test run.
Magic Eden12

Get a Wallet's Activities

ActionIn the docs only

Returns what one wallet has been doing on Magic Eden, a history you can drop into a log or a note in your CRM.

When to use it
an accountant helping a client reconstruct past trades wants the wallet's movements exported instead of copied line by line.
Watch out
the doc does not say how far back the history goes, so do not promise anyone a complete record before checking the output.
Magic Eden13

Get a Wallet's Escrow Balance

ActionIn the docs only

Reads the amount one wallet holds in escrow on Magic Eden, a single figure your scenario can compare, format or report.

When to use it
a trader wants a chat alert when the escrow figure moves, instead of opening the marketplace to look.
Watch out
this module only reads the current balance, so spotting a change means storing the previous value somewhere, such as a sheet row.
Magic Eden14

Get a Wallet's Information

ActionIn the docs only

Gets the profile Magic Eden keeps for one wallet, useful to enrich a record before anything else happens to it.

When to use it
in a scenario started by another app, such as a form where a buyer leaves a wallet, add it first to see what Magic Eden knows about that wallet.
Watch out
it reads and never changes anything, so testing is safe, apart from the operations each test uses.
Magic Eden15

Get a Wallet's Tokens

ActionIn the docs only

Lists the tokens held by one wallet, the inventory view most wallet scenarios start from once the wallet is known.

When to use it
a gallery that manages a shared wallet wants its current holdings mirrored in a sheet the whole team can read.
Watch out
if each token comes back as its own bundle, chaining Get a Token's Metadata after it runs that module once per token.
Magic Eden16

Make an API Call

ActionIn the docs only

Opens the rest of the Magic Eden API from inside your scenario, with the same connection as the other modules, for any request the 15 ready-made modules leave out.

When to use it
you need data from an endpoint none of the Get modules reaches, and you already know which request to send.
Watch out
you write the request yourself from Magic Eden's API documentation, since Make's page for this app stays limited.
Need help

Need help automating Magic Eden with Make?

A person reads every message.

FAQ

Magic Eden and Make: common questions

01Is the Magic Eden Make integration free?
Yes. Magic Eden is a standard app in Make, so its modules work from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Every module run counts as an operation, so a scenario that reads many wallets consumes more of the monthly credits of your plan.
02What do you need to connect Magic Eden to Make?
A Make account and access to your Magic Eden account. Make's documentation lists no prerequisite and no official connection steps for this app, so you follow the generic path: add a Magic Eden module, click Create a connection, name it if you want, authorize Make or paste the key Magic Eden gives you, then save. The connection is stored once and shared by all 16 modules, Make an API Call included. If the authorization screen asks for something unclear, Magic Eden's own documentation is the place to look, since Make flags its coverage as limited.
03Does the Magic Eden Make integration react in real time?
No, not by itself. Magic Eden has no trigger module in Make: all 16 modules are actions that read data when the scenario reaches them. You still have two ways to start a scenario. Set a schedule on the first module, every 15 minutes by default and never shorter than that on the Free plan. Or open the scenario with a trigger from another app, such as a form or a spreadsheet, and let that app decide when the Magic Eden modules run.
04What if a Magic Eden module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Magic Eden API from your scenario, with the same connection as the other modules, so you are not limited to the 15 ready-made Get modules. The catch is that you write the request yourself, and Make's documentation is openly limited for this app, for lack of public information. Keep Magic Eden's API documentation open while you build, and test each call with Run once before you switch the scenario on.
05Make or n8n for Magic Eden?
It depends on the data you need. On Make, Magic Eden offers 16 modules, all actions that read wallets, tokens, collections and offers, plus Make an API Call for the rest of the API, and all of it works from the Free plan. n8n often has a node for the same app, so look at its catalog before choosing. Neither tool is ranked here: list the reads your project requires, then check which tool covers them with ready-made modules and which would leave you writing API requests.
Same platform

Other docs you might need on this stack.

Browse all integrations