Resources · Make integration

Transistor.fm Make integrationAutomate Transistor.fm with Make.

What if a new episode or a new subscriber on your podcast set the rest of your work in motion? The Transistor.fm Make integration offers 11 modules, 4 of them instant triggers. This page is for podcasters who have never built an automation: you link your account, then build a first working flow.

Try the Transistor.fm integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Transistor.fm Make integration do?

The Transistor.fm Make integration links your podcast host to Make, a no-code automation tool. In Make you build a scenario, the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search. Here, those bricks react to your episodes and manage the subscribers of your shows.

Announce every release. Watch Episode Published fires the moment an episode goes live, and the next module passes the news to another tool your listeners or your team already read. Watch Episode Created fires as soon as an episode is created, usually before it goes live, which suits a producer who prepares show notes ahead.

Keep your subscriber list in step with sales. When a customer buys access in another app, Create a Subscriber adds them to your show. When they cancel, Delete a Subscriber by Email removes them, even if you only know their address.

Follow who comes and goes. Watch New Subscriber and Watch Deleted Subscriber tell you about each change, so a CRM or a spreadsheet can record it. List Subscribers and Get a Subscriber help when you need to check a record before acting.

The listed modules cover episodes only through triggers: nothing here creates or edits an episode. For anything else the Transistor.fm API offers, Make an API Call reuses the same connection. The same app often exists as an n8n node too; the n8n vs Make page sets out the differences. To learn the editor at your own pace, see our Make training, and before picking a plan, read Make pricing.

Connect

How do you connect your Transistor.fm account to Make?

  1. 01

    Copy your API key

    In your Transistor.fm dashboard, open the account area and copy the API key shown there. You need an active Transistor.fm account for this key to exist. Keep it at hand, Make asks for it in a moment.

  2. 02

    Add a module and open the connection

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you run several shows or accounts. Paste the API key you copied, confirm, and Make can now read your subscribers.

First scenario

Your first scenario: turn each sale into a subscriber

GoalWhen a customer buys access in your online shop, Make adds them as a subscriber on Transistor.fm.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. The first module comes from the app where the sale happens, such as your shop.

  2. 02

    Set up the sale trigger

    Pick that app's module that watches new orders and link its account. This module starts the flow and hands each order to the next one as a bundle, one item at a time.

  3. 03

    Add Create a Subscriber

    Click the + to the right, search Transistor.fm and choose Create a Subscriber. Click Create a connection, paste your API key, then map the buyer's details from the order.

  4. 04

    Test with Run once

    Click Run once with a test order waiting. Each module shows the bundle it received, so you can check the new subscriber in Transistor.fm before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each order it picks up now becomes a subscriber without manual entry.

Triggers

What can start a Transistor.fm scenario?

4 modules start a scenario when something happens in Transistor.fm. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Transistor.fm as soon as it happens.

Transistor.fm1Watch Deleted Subscriber

Watch Deleted Subscriber

Instant trigger

In Make“Watches for a deleted subscriber.”

You learn right away that someone has been removed from one of your shows, so the other tools you run can forget them too. The scenario receives that subscriber as a bundle and can pass their details to the next module.

How it fires
instant, Transistor.fm calls Make through a webhook as soon as the subscriber is deleted.
When to use it
a listener leaves a paid show and you want your CRM or member list to drop them without anyone checking by hand.
Watch out
it only reports the removal; to also clean another app, add that app's module after it.
Transistor.fm2Watch Episode Created

Watch Episode Created

Instant trigger

In Make“Watches for an episode created.”

Your scenario starts as soon as a new episode exists in Transistor.fm, before it reaches listeners. That gives a producer time to prepare show notes, a task list or a draft post while the audio is still being finished.

How it fires
instant, the app calls Make through a webhook the moment the episode is created.
When to use it
your team works on each episode in steps and needs a card or a task opened when production begins.
Watch out
a created episode is usually not public yet, so keep public announcements for Watch Episode Published.
Transistor.fm3Watch Episode Published

Watch Episode Published

Instant trigger

In Make“Watches for an episode published.”

This one tells Make that an episode has just gone live, which is the moment most podcasters want to spread the word. The episode arrives as a bundle, ready to be mapped into a message, a newsletter draft or a spreadsheet row.

How it fires
instant, Transistor.fm warns Make through a webhook as soon as the episode is published.
When to use it
you want every release announced in your community or logged in a content calendar, with no copy and paste.
Watch out
test with a real publication during Run once, since the trigger waits for the event.
Transistor.fm4Watch New Subscriber

Watch New Subscriber

Instant trigger

In Make“Watches for a new subscriber.”

Each person added to one of your shows starts the scenario, so you can welcome them or record them elsewhere without delay. The new subscriber comes through as a bundle that the following modules can read.

How it fires
instant, the app pings Make through a webhook as soon as the subscriber is added.
When to use it
a new listener of a members-only show should get a welcome email or appear in your CRM.
Watch out
if another scenario adds subscribers with Create a Subscriber, this trigger will fire for those too, so avoid building a loop between the two.
Modules

What can Make do in Transistor.fm?

Transistor.fm gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Transistor.fm1

Create a Subscriber

Action

In Make“Creates a subscriber.”

Adds a person to your show from data another app sends, so access follows a purchase or a signup without manual entry.

When to use it
a customer pays for a membership in your shop and should join your show at once.
Watch out
run a Get a Subscriber or List Subscribers check first if the same person might already be on the list.
Transistor.fm2

Delete a Subscriber by Email

Action

In Make“Removes a subscriber by email.”

Removes someone from your show using only their email address, which is usually the one detail every other tool shares.

When to use it
a cancellation arrives from your billing or form tool, and all you receive is the customer's address.
Watch out
no listed module restores a removed subscriber, so test with your own address before switching it on.
Transistor.fm3

Delete a Subscriber by ID

Action

In Make“Remove a subscriber by ID.”

Takes a subscriber off your show when you already hold their Transistor.fm ID, for example from a trigger or a search earlier in the flow.

When to use it
choose it over the email version when a previous module already returned the exact subscriber, so no address matching is needed.
Watch out
map the ID from that earlier module rather than typing it, or every run hits the same person.
Transistor.fm4

Get a Subscriber

Action

In Make“Gets a subscriber.”

Fetches the record Transistor.fm holds for one subscriber so the next modules can use their details, instead of relying on partial data from another app.

When to use it
before updating or removing someone, you want to confirm who they are and read what Transistor.fm holds on them.
Watch out
it returns a single subscriber; to scan the whole audience, List Subscribers is the right module.
Transistor.fm5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Transistor.fm API through the connection you already set up, which covers what the ready-made modules leave out.

When to use it
you need an action on episodes or shows, if the Transistor.fm API offers it, since the ready-made modules handle subscribers only.
Watch out
you write the request yourself, so keep the Transistor.fm API documentation open while you build it.
Transistor.fm6

Update a Subscriber

Action

In Make“Modifies a subscriber.”

Changes an existing subscriber's record so Transistor.fm stays accurate when their details move in another tool, without deleting and adding them again.

When to use it
a member changes their details in your membership platform and the podcast feed should follow.
Watch out
point it at the right person by mapping the result of Get a Subscriber or a trigger, never a guessed value.
Transistor.fm7

List Subscribers

Search

In Make“Lists a subscribers.”

Returns the subscribers of your show as separate bundles, zero, one or many, so each one can go through the rest of the scenario.

When to use it
you want to copy your audience into a spreadsheet or compare it with the customer list of another app.
Watch out
each returned bundle runs the following modules once, and every run counts as an operation on your Make plan.
Need help

Need help automating Transistor.fm with Make?

A person reads every message.

FAQ

Transistor.fm and Make: common questions

01Is the Transistor.fm Make integration free?
Yes, on the Make side. Transistor.fm is a standard app, available from the Free plan onward. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the minimum interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, and each module running on one bundle is one of them. Your Transistor.fm subscription is separate and not covered here.
02What does the Transistor.fm Make connection require?
You need an active Transistor.fm account and its API key. The key sits in the account area of your Transistor.fm dashboard, where you can copy it. In Make, add a Transistor.fm module, click Create a connection, optionally give the connection a name, and paste the key. With one of the instant triggers, click Create a webhook first, then Create a connection. The connection is saved once and every other Transistor.fm module in your scenarios reuses it.
03Do the Transistor.fm triggers in Make react in real time?
Yes. All four Transistor.fm triggers are instant: Watch Deleted Subscriber, Watch Episode Created, Watch Episode Published and Watch New Subscriber. Transistor.fm calls Make through a webhook as soon as the event happens, so the scenario does not wait for the 15 minute default schedule that applies to scheduled triggers. This also means a test with Run once needs a real event, such as publishing an episode or adding a subscriber, while the editor is listening.
04What if a Transistor.fm module is missing in Make?
Use Make an API Call. It sends any request the Transistor.fm API supports with the connection you already created, which is useful because the ready-made actions cover subscribers only: creating, reading, listing, updating and deleting them. For episodes or shows beyond the two episode triggers, that module is the route, provided the Transistor.fm API offers the call. The Make documentation for this app notes that it was partly generated with AI, so check important details with Transistor.fm directly.
05Make or n8n for Transistor.fm?
It depends on which tool your team already works in. Make offers 11 ready-made Transistor.fm modules, including four instant triggers and a generic API call, inside a visual editor where a first scenario takes only a few steps. The same app often has an n8n node as well. Compare the modules each tool lists for Transistor.fm against the flow you have in mind, and choose the one whose modules match it with the least custom work.
Same platform

Other docs you might need on this stack.

Browse all integrations