Resources · Make integration

Steady Make integrationAutomate Steady with Make.

Your Steady members, plans and subscriptions can feed the rest of your tools on their own. The Steady Make integration gives you 6 modules: 3 actions and 3 searches. This page is for publishers who run a Steady publication, and it walks you from connection to a working first scenario.

Try the Steady integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Steady Make integration do for you?

The Steady Make integration links your Steady publication to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick of that chain. With Steady, those bricks read your publication, your plans, your members and your newsletter list, and one of them can cancel a subscription.

A clean member list in your other tools. List Subscriptions returns every current subscription of the publication. Each one comes out as a bundle, one item passed to the next module, so a spreadsheet or CRM module placed after it can store one row per paying member.

Cancellations handled from a form. When a supporter asks to stop through a form in another app, Cancel a Subscription ends it while respecting the end of the current term. Nobody has to open the Steady backend for it.

A view of your free readers too. List Newsletter Subscribers returns the people who get your newsletter, and List Plans returns the plans you sell. Put both side by side to see who reads you for free and what you offer to paying members.

Steady has no trigger in Make: nothing starts a scenario from inside Steady. You start it with Make's own schedule, or with a trigger from another app. Anything the six modules do not cover goes through Make an API Call. The Make documentation for Steady is flagged as AI-generated, so check important details with Steady itself.

Still weighing the two platforms? Read n8n vs Make, and check Make pricing before counting operations. If you would rather hand the build over, the Make agency team can take it.

Connect

How do you connect your Steady account to Make?

  1. 01

    Copy your API key in Steady

    Open the backend of your publication in Steady, click the Integration menu in the sidebar, then API. Copy the API key shown on that page. You need an active Steady account for this, or registered OAuth app credentials instead.

  2. 02

    Add a Steady module and open the connection

    In your scenario, add any Steady module and click Create a connection. A connection is your Steady account linked to Make once; every Steady module of your scenarios reuses it. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and confirm

    Paste the API key you copied from Steady, or follow the instructions Make shows on screen, then save. From now on, Make can read your publication, and the dropdowns of the Steady modules fill with data from your account.

First scenario

Your first scenario with Steady

GoalWhen a supporter fills in a cancellation form in another app, Make cancels the matching Steady subscription at the end of the current term.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the +. Steady has no trigger, so the first module comes from the app where your form lives.

  2. 02

    Place the form trigger

    Search for your form app by name, pick its module that watches new answers, and connect that account. Each new answer will arrive as one bundle.

  3. 03

    Add Cancel a Subscription

    Click the + on the right of the first module, search for Steady and pick Cancel a Subscription. Choose your Steady connection, then map the data from the form to tell Make which subscription to end.

  4. 04

    Test with Run once

    Send one test answer through your form, then click Run once. Open the bubbles above each module to read the bundles they received and check that the right subscription was targeted.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on.

Modules

What the Steady modules do

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

Steady1

Cancel a Subscription

Action

In Make“Cancels a subscription respecting the end of the current term.”

This module stops a paying member's subscription for you, and the member keeps access until the end of the term already paid for. You get a clean exit without cutting anyone off early.

When to use it
a supporter asks to leave through a form or an email and you want the request processed without logging into Steady.
Watch out
the action changes a real subscription, so test it with Run once on your own account before you connect a live form.
Steady2

Get a Publication

Action

In Make“Returns infos about the publication associated with the API key.”

Reading your publication details is what Get a Publication gives you: Make returns the information about the publication linked to the API key of the connection. It makes a handy first test after connecting.

When to use it
you want to check which publication a connection points to, or to reuse its details further down the scenario.
Watch out
it returns the publication behind the key, so a second publication most likely needs its own connection.
Steady3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Steady API from your scenario, reusing the connection you already created. It fills the gaps the five other modules leave open.

When to use it
you need something none of the listed modules does, and the Steady API documentation describes the request to send.
Watch out
this is the most technical module of the list, since you write the request yourself; keep the named modules for everything they already cover.
Steady4

List Newsletter Subscribers

Search

In Make“Returns an array with all current newsletter subscribers of the publication.”

Your whole current newsletter audience comes back from this search, one bundle per subscriber, ready to be copied into a sheet, a CRM or an email tool placed after it.

When to use it
you want your free readers in another tool, for example to compare them with your paying members.
Watch out
every subscriber becomes a bundle, and each module that follows runs once per bundle, which adds operations to your plan.
Steady5

List Plans

Search

In Make“Returns an array with all plans of the publication.”

Here you receive every plan your publication offers, each as its own bundle. It is the reference list to label members or to build a price overview somewhere else.

When to use it
you sync subscriptions into another tool and want each row to carry the name of the plan it belongs to.
Watch out
a search can return zero, one or several bundles, so plan what the next module does with each of them.
Steady6

List Subscriptions

Search

In Make“Returns an array with all current subscriptions of the publication.”

All current subscriptions of the publication land in your scenario through this search, one bundle each. That gives you an up-to-date list of paying members to push anywhere.

When to use it
you want a member table in a spreadsheet or a CRM that follows what happens in Steady.
Watch out
it returns current subscriptions only, so keep a copy in your own tool if you need the history of past members.
Need help

Need help automating Steady with Make?

A person reads every message.

FAQ

Steady Make integration: common questions

01Is the Steady Make integration free?
Yes, Steady is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 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 count usage in operations per month. You still need your own active Steady account.
02What do you need to connect Steady to Make?
You need an active Steady account and either an API key or registered OAuth app credentials. The API key sits in the backend of your publication: open the Integration menu in the sidebar, click API and copy the key. In Make, add a Steady module, click Create a connection, name it if you like, and paste the key. Get a Publication returns the publication behind that key, which suggests one key per publication. Once the connection exists, every Steady module in your scenarios reuses it, and Make fills the dropdowns with data it can read from your publication.
03Does the Steady Make integration react in real time?
No, because Steady has no trigger in Make, neither scheduled nor instant. A scenario that uses Steady starts another way: with Make's own schedule on the first module, every 15 minutes by default, or with a trigger from another app, such as a form that receives a cancellation request. The Steady modules then run as the following steps of the scenario. Since a Steady search can return many bundles, each following module runs once per bundle, so keep an eye on the operations your plan counts.
04What if a Steady module is missing in Make?
Use Make an API Call. It calls any endpoint of the Steady API with the connection you already created, so you are not limited to the five named modules. You write the request yourself, following the Steady API documentation. Also note that Make flags its Steady documentation as AI-generated and advises checking important details directly with Steady. Before you build a request by hand, check whether one of the listed modules already returns what you need, since those are simpler to set up and to test with Run once.
05Should you use Make or n8n for Steady?
It depends on your criteria rather than on a winner. In Make, Steady comes with six modules, one connection reused by all of them, and Make an API Call for the rest. n8n often has a node for the same app, so check whether one exists for Steady and compare what each covers for your case. The team's comparison page goes through both tools criterion by criterion. Start from what you need to automate: listing members, reading plans or cancelling subscriptions, then test the same scenario in both tools before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations