Resources · Make integration

Steam Make integrationAutomate Steam with Make.

Want your Steam library and game news to land where your team already works? The Steam Make integration gives you 4 modules: three searches and one open API call. This page walks you through the API key, the connection and a first working scenario.

Try the Steam integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Steam Make integration do for you?

The Steam Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) read data from Steam: the games a profile owns, the games it played in the last two weeks, and the news published about a game. You then send that data to any other app Make supports, without writing code.

A news digest for a game you follow. A studio or a community manager points List News for App at one game and forwards each item to a team chat or a spreadsheet. Each news item arrives as a bundle, meaning one item passed from one module to the next.

A library snapshot. List Owned Games pulls the games tied to a profile ID, so a gaming club or a streamer can keep an up-to-date list in a table such as the one described on the Airtable Make integration page.

A recent activity feed. List Recently Played Games returns what a profile played over the last two weeks, handy for a community newsletter or a personal play log.

Know the limits before you build. Steam has no trigger in Make, so a scenario starts on a schedule or on another app's event. The three searches only read data. Anything else in the Steam Web API goes through Make an API Call, which reuses the same connection. The official Make doc for Steam also warns that it was generated by AI and may contain mistakes, so check key details on Steam's side.

If you are still choosing a platform, the n8n vs Make comparison sets the criteria side by side, and the Make training covers scenario building from scratch.

Connect

How do you connect your Steam account to Make?

  1. 01

    Create a Web API key in Steam

    In your Steam account, open Users and Permissions, then Manage Groups. Pick or create a group for Web API key access, click Create WebAPI Key, choose the permissions, then Save Changes.

  2. 02

    Copy the key from the sidebar

    Once saved, Steam shows the API key in the right-hand sidebar. Copy it now. Make needs this key, together with a Steam account, before any Steam module can run.

  3. 03

    Add a Steam module and create the connection

    In your scenario, add any Steam module and click Create a connection. Give it a name in Connection name if you like, paste the key, and save. That connection is then reused by every Steam module.

First scenario

Your first Steam scenario in Make

GoalWhen a profile has played games recently, Make fetches the latest news for each of those games.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add List Recently Played Games

    Search for Steam, pick List Recently Played Games and select the connection you created. Fill in the profile the module should read.

  3. 03

    Chain List News for App

    Click the + on the right of the first module, add List News for App and map the game coming from the previous module, so each played game gets its own news lookup.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received: the games first, then the news items for each game.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Pick your interval and switch the scenario on.

Modules

What the Steam modules do in Make

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

Steam1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the Steam Web API that the three listed searches leave out, using the connection you already set up. You write the request, Make adds your credentials.

When to use it
a Steam endpoint you need has no dedicated module, and you would otherwise be stuck.
Watch out
You write the request yourself here, so read Steam's own API reference before you send anything.
Steam2

List News for App

Search

In Make“Gets all news about specified app.”

Get every news item published about a given game, each one as its own bundle that you can post, store or filter further down the scenario.

When to use it
a studio, a publisher or a fan community wants the updates of one title copied into a chat channel or a shared sheet.
Watch out
as a search, it can return zero, one or many items, so add a filter if you only care about some of them.
Steam3

List Owned Games

Search

In Make“Gets a list of owned games by profile ID.”

Pull the full list of games owned by a Steam profile, found through its profile ID, and turn a library into rows you can sort and count elsewhere.

When to use it
a club, a reviewer or a streamer wants an inventory of titles kept in a spreadsheet or a database.
Watch out
each game comes out as a separate bundle, and each later module runs once per game, which adds operations on your plan.
Steam4

List Recently Played Games

Search

In Make“Gets a list recently played games of two weeks on specified account.”

See what a Steam account has played over the last two weeks, a short window that reflects current activity rather than the whole library.

When to use it
you publish a "recently played" section in a community newsletter, or you keep a personal play diary.
Watch out
an account with no play in that window returns nothing, so the rest of the scenario simply gets no bundle to work on.
Need help

Need help automating Steam with Make?

A person reads every message.

FAQ

Steam and Make: frequent questions

01Is the Steam Make integration free?
Yes. Steam is a standard app in Make, so it is available from the Free plan. The Free plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and lift the cap on active scenarios. Each module run on one bundle counts as an operation, which is how Make measures your usage.
02What do you need to connect Steam to Make?
You need a Steam account and a Steam Web API key. You create the key in your Steam account under Users and Permissions, then Manage Groups, by picking a group, clicking Create WebAPI Key, choosing the permissions and saving. Steam then shows the key in the right-hand sidebar. In Make, add any Steam module, click Create a connection, give it a name if you want, and paste the key. Every Steam module then reuses that same connection.
03Does the Steam Make integration react in real time?
No. Steam has no trigger module in Make, scheduled or instant, so nothing in Steam can start a scenario by itself. Two options remain. You can put a Steam search first and let the scenario run on its schedule, every 15 minutes by default, or as often as once a minute on a paid plan. Or you can start the scenario with a trigger from another app and call the Steam modules after it when that app has something new.
04What if the Steam module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Steam Web API with the connection you already have, so you are not limited to the three searches Make lists for owned games, recent play and app news. You write the request yourself, which takes a look at Steam's API documentation. Also keep in mind that Make's own Steam doc is flagged as AI-generated and may contain mistakes, so verify important details with Steam.
05Should you use Make or n8n for Steam?
It depends on your criteria, not on a winner. On Make, Steam offers four modules: three read-only searches and Make an API Call for the rest, all behind one API key connection and a visual editor where you test with Run once. Before you commit, check whether n8n offers a Steam node that covers the same data, then compare how each tool handles scheduling and usage for your volume. Pick the one your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations