Resources · Make integration

SpaceX Make integrationAutomate SpaceX with Make.

Need launch, rocket or crew data flowing into your own tools? The SpaceX Make integration gives you 29 modules: 16 that fetch one record and 13 that search lists. This page shows how to connect the app, build a first scenario and pick the right module.

Try the SpaceX integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the SpaceX Make integration?

The SpaceX Make integration lets a Make scenario (the automation you build, a chain of modules) read SpaceX data: launches, rockets, capsules, crews, ships, landing pads and Starlink satellites. Every piece of data arrives as a bundle, one item that moves to the next module, so you can send it to a sheet, a chat or a newsletter tool.

A launch briefing for a content team. Get the Next Launch and Get the Latest Launch sit side by side in one scenario, and their bundles go to the app where your editor writes. The draft starts from data, not from a browser tab.

A reference table for a space club or a classroom. Search Rockets, Search Launchpads and Search Landpads each return a list, one bundle per item, which you can drop row by row into a spreadsheet module of another app.

A crew and payload lookup on demand. When another app starts the scenario, Get a Crew Member or Get a Payload fetches the one record you need and passes it on.

What Make does not do here: SpaceX has no trigger, so nothing in SpaceX starts a scenario by itself. You start it on a schedule or from another app. Make also warns that the documentation for this app is limited, because little public information exists about it; test each module before relying on it. When a listed module falls short, Make an API Call reaches other endpoints with the same connection.

New to the tool? The Make training covers the editor from zero, and the Make review sums up what it does well and less well. If you are weighing both tools, read n8n vs Make.

Connect

How do you connect SpaceX to Make?

  1. 01

    Add a SpaceX module

    In a scenario, click the +, search for SpaceX and pick any module, for example Get the Next Launch. Then click Create a connection. A connection is your SpaceX access linked to Make once, and every SpaceX module reuses it.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear name helps when you open the scenario again later and wonder which access a module is using.

  3. 03

    Authorize and save

    Follow what the window asks: authorize Make on the page it opens, or paste the key it requests. Click Save. The module can now read SpaceX data, and Make fills its lists for you.

First scenario

Your first scenario with SpaceX

GoalWhen the scenario runs on its schedule, Make fetches the next SpaceX launch and the latest one, ready to be sent to another app.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Everything you build next hangs off this first bubble.

  2. 02

    Add Get the Next Launch

    Search for SpaceX, choose Get the Next Launch and click Create a connection if you have none yet. This module returns one bundle: the upcoming launch.

  3. 03

    Add Get the Latest Launch

    Click the + on the right of the first module and add Get the Latest Launch. Now one run carries both the launch that happened last and the one coming up.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows a bubble above each module; open it to read the bundle. Check the data before you connect a destination app.

  5. 05

    Schedule and switch it on

    Click the clock on the first module. A new scenario runs every 15 minutes by default; the Free plan keeps 15 minutes as the minimum. Pick your interval, then switch the scenario on.

Modules

What each SpaceX module does

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

SpaceX1

Get Company Info

ActionIn the docs only

This module brings the SpaceX company profile into your scenario as one bundle, so later modules can reuse it instead of someone pasting a paragraph by hand. It is the general card, not a record about a single vehicle.

When to use it
an internal report or a school handout needs a short company section filled from the app.
Watch out
read the bundle after a Run once before mapping it, since the app documentation stays thin.
SpaceX2

Get a Capsule's Info

ActionIn the docs only

You get the record of one capsule, and only that one, handed to the next module as a single bundle. It fits a scenario that already knows which capsule matters and just needs its details.

When to use it
a mission page you maintain mentions a specific capsule and you want its data pulled in rather than typed.
Watch out
if you do not know which capsule yet, start with Search Capsules instead.
SpaceX3

Get a Core

ActionIn the docs only

Pick one booster core and Make returns its record, ready to map into a sheet or a message. One core, one bundle, one operation for the step that follows.

When to use it
a fan newsletter follows one reused booster and each issue should show its current record next to the text.
Watch out
tracking every core at once is a job for Search Cores, not for many copies of this module.
SpaceX4

Get a Crew Member

ActionIn the docs only

Pulls the profile of a single crew member into the scenario so a bio card or a slide can be built from it automatically. Nothing else comes with it: no list, no other astronauts.

When to use it
a form or another app sends a name, and the scenario must answer with that person's record.
Watch out
Make cannot guess the person for you; the module needs to be told which crew member to read.
SpaceX5

Get a Dragon

ActionIn the docs only

Returns one Dragon record so the details of that spacecraft type travel through your scenario as a single bundle. Unlike Get a Capsule's Info, the focus here is the Dragon entry itself.

When to use it
an explainer article compares spacecraft and one section should always show the Dragon data straight from the app.
Watch out
to see every Dragon entry, Search Dragons returns the whole set.
SpaceX6

Get a Landpad

ActionIn the docs only

Fetches the record of one landing pad, handy when a message about a landing should name the place and show its details. The output is one bundle you can map anywhere.

When to use it
a launch recap written by the scenario needs the landing site described, not just referenced.
Watch out
landing pads and launchpads are two separate modules; picking the wrong one returns the wrong kind of site.
SpaceX7

Get a Launch

ActionIn the docs only

Gives you the full record of one launch you already have in mind, past or upcoming. That precision is what separates it from the latest and next launch modules, which choose the launch for you.

When to use it
a history timeline in Notion or a sheet gets one entry per anniversary launch that someone selected.
Watch out
a single launch means one bundle; for a range of launches, a search module does the job.
SpaceX8

Get a Launchpad

ActionIn the docs only

This one reads a single launchpad and sends its record forward, so the place a rocket leaves from can appear in your output with real data behind it.

When to use it
a post about the next launch should include a short paragraph on the pad, filled by the scenario rather than by memory.
Watch out
for a table of every pad, Search Launchpads is cheaper than repeating this module.
SpaceX9

Get a Payload

ActionIn the docs only

Fetches what one mission carried: a single payload record, delivered as one bundle to the next module. Useful when the cargo is the story, not the rocket.

When to use it
a satellite operator's marketing team wants the record of its own payload dropped into a press kit document.
Watch out
the module does not list payloads; you have to know which one you want or run Search Payloads first.
SpaceX10

Get a Rocket

ActionIn the docs only

Returns the record of one rocket model so its data can be reused in a card, a slide or a chat reply. Short scenario, clear result.

When to use it
a classroom quiz tool needs the facts of the rocket used in today's lesson, pulled from SpaceX instead of retyped.
Watch out
do not confuse it with Get a Core, which reads a single physical booster rather than a rocket model.
SpaceX11

Get a Ship

ActionIn the docs only

Brings in the record of one SpaceX ship, one of the vessels in the fleet, as a single bundle ready to map. Maritime side of the missions, in one step.

When to use it
a recovery story in a newsletter should show the ship involved alongside the launch data.
Watch out
if the recap covers the whole fleet, Search Ships avoids building one module per vessel.
SpaceX13

Get the Latest Launch

ActionIn the docs only

Make hands you the most recent SpaceX launch without asking which one: the module picks it. Ideal for a recap that always talks about what just happened.

When to use it
a Slack channel for space fans gets a post summing up the last launch whenever the scenario runs.
Watch out
the module picks the launch itself, so two runs close together can bring back the same record; make sure the destination does not post it twice.
SpaceX14

Get the Next Launch

ActionIn the docs only

The upcoming launch arrives as one bundle, chosen by the module, so a countdown or a preview can be written from live data. No search, no selection on your side.

When to use it
an events page or a calendar app should always show the next launch that SpaceX lists.
Watch out
each run brings a fresh bundle, so update the entry in the destination rather than creating a new one every time.
SpaceX15

Get the Roadster

ActionIn the docs only

This module returns the Roadster record, a single entry that SpaceX exposes on its own. It needs no selection: there is only one.

When to use it
a fun fact widget on a science blog or a Discord bot command should answer with the Roadster data in one step.
Watch out
as with the other SpaceX modules, the documentation is limited, so look at a Run once result before building a message around it.
SpaceX16

Make an API Call

ActionIn the docs only

When none of the other SpaceX modules covers your need, this one calls any endpoint of the SpaceX API with the connection you already have. It is the escape hatch, not the first choice.

When to use it
a data team wants a filter or a combination of data that no listed module offers.
Watch out
you write the request yourself, and with the documentation limited you will need to test each call with Run once.
SpaceX17

Search Capsules

SearchIn the docs only

Returns every capsule that matches, one bundle per capsule, which turns a single step into a full list for your spreadsheet or database. Zero results is also a possible answer.

When to use it
a museum or school project builds a capsule inventory in Airtable.
Watch out
each bundle makes the next module run again, and every run counts as an operation, the unit Make counts on your plan.
SpaceX18

Search Cores

SearchIn the docs only

Lists booster cores, one bundle each, so you can track reuse across the fleet in a single table instead of fetching cores one by one.

When to use it
an analyst keeps a sheet of every core and wants it filled by the scenario.
Watch out
sending each result to another app multiplies operations; group the bundles with an aggregator of Make if the destination accepts a batch.
SpaceX19

Search Crews

SearchIn the docs only

Returns crew members as a list, which makes a roster page or a directory easy to fill without a manual lookup for each astronaut.

When to use it
an education site publishes a gallery of crew profiles and wants a fresh source for it.
Watch out
a search can come back empty, and the next module then does not run; test that case with Run once too.
SpaceX20

Search Dragons

SearchIn the docs only

Gets all the Dragon entries that match, one bundle per entry, so a comparison table of versions builds itself.

When to use it
a blog post compares Dragon versions and the table below the text should come from SpaceX data, refreshed when the scenario runs.
Watch out
writing one row per bundle in a sheet is fine, but posting each one to a chat would flood the channel.
SpaceX21

Search Landpads

SearchIn the docs only

Brings back the landing pads as a list, one item per pad, ready to fill a map layer or a reference sheet in a single run.

When to use it
a geography teacher or a travel blogger maps every SpaceX landing site in Google Sheets.
Watch out
launchpads are not included; pair this module with Search Launchpads when the map should show both kinds of site.
SpaceX22

Search Launches

SearchIn the docs only

Returns the launches that match, one bundle for each. Next to Search Past Launches and Search Upcoming Launches, it is presumably the broadest launch search, with no split between past and future.

When to use it
a research project needs a complete launch table as its starting point.
Watch out
the result can be long; if you only care about one side of the calendar, Search Past Launches or Search Upcoming Launches keep the list and your operations smaller.
SpaceX23

Search Launchpads

SearchIn the docs only

Returns the launchpads that match, one bundle per pad, so the departure sites of every mission can live in one table you control.

When to use it
a travel agency planning launch-viewing trips keeps a sheet of pads for its guides.
Watch out
landing pads come from Search Landpads, a separate module, even though the names sound close.
SpaceX24

Search Past Launches

SearchIn the docs only

Only launches that already happened come back here, one bundle each, which gives a clean archive without future entries mixed in.

When to use it
a statistics dashboard or an anniversary post draws on launches that are done.
Watch out
the archive keeps growing, so map only the data you need and check how many operations a full run uses before switching the scenario on.
SpaceX25

Search Payloads

SearchIn the docs only

Lists payloads, the cargo carried by the missions, one per bundle. It answers questions about what was flown rather than how.

When to use it
a satellite industry newsletter compiles the payloads that match its topic into a Notion database.
Watch out
once you have picked the payload you care about, Get a Payload is lighter for later runs.
SpaceX26

Search Ships

SearchIn the docs only

Returns the SpaceX fleet as a list of bundles, one ship each, which makes a vessel directory or a recovery overview simple to keep current.

When to use it
a maritime enthusiast group shares a sheet of every ship with its members.
Watch out
if the next module only needs one vessel, a Get a Ship module saves the operations spent on the others.
SpaceX28

Search Upcoming Launches

SearchIn the docs only

Returns only launches still to come, one bundle each, so a schedule of what is next can be built without filtering out the past.

When to use it
a community calendar in Google Calendar or Notion lists every announced launch for its members.
Watch out
the same launches come back on every run, so update the events you created instead of adding duplicates.
SpaceX29

Search rockets

SearchIn the docs only

Brings back rocket models as a list, one per bundle: a short catalog that fills a comparison table in a single step.

When to use it
a science teacher prepares a side-by-side rocket sheet for a class project.
Watch out
for a single model you already know, Get a Rocket spends fewer operations than a full list.
Need help

Need help automating SpaceX with Make?

A person reads every message.

FAQ

SpaceX and Make: common questions

01Is the SpaceX Make integration free?
Yes. SpaceX is a standard app in Make, so its 29 modules work on the Free plan. That plan has limits worth knowing: 2 active scenarios, a scheduled run no more often than every 15 minutes, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module that runs on a bundle counts as one operation. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution.
02What do you need to connect SpaceX to Make?
The Make documentation lists no prerequisite for SpaceX. Add any SpaceX module, click Create a connection, give it a name if you like, then authorize Make or paste the key the window asks for, and click Save. The connection is then shared by every SpaceX module in your scenarios. Make notes that the documentation for this app is limited, so test the connection with Run once before building on it.
03Does SpaceX trigger Make scenarios in real time?
No. SpaceX has no trigger in Make, neither scheduled nor instant, so nothing in SpaceX can start a scenario. Two ways around it. First, a schedule: set the clock on the first module; a new scenario runs every 15 minutes by default, 15 minutes is the Free plan minimum and paid plans go down to 1 minute. Second, place a trigger of another app first, and the SpaceX modules run whenever that app starts the scenario.
04What if the SpaceX module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the SpaceX API with the same connection, which covers what the listed modules leave out. Keep in mind that Make flags the documentation for this app as limited, because little public information exists about SpaceX. Test each request with Run once and read the returned bundle before mapping it. The Make troubleshooting page on this site helps when a run fails.
05Should you use Make or n8n for SpaceX?
It depends on where you already work. In Make, SpaceX offers 29 modules, 16 that fetch a single record and 13 searches, plus Make an API Call for the rest, and it runs on the Free plan. The same app often has an n8n node as well, so check whether one exists before choosing. If your other scenarios live in Make, keeping SpaceX there avoids a second tool; the n8n vs Make comparison on this site lays out the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations