Transistor

Transistor.fm is podcast hosting with private podcasts, per-episode analytics, and webhooks. Agents create, update, and publish episodes, upload audio, manage private subscribers, pull show and episode analytics, and react to Transistor events in real time.

Verified 1 trigger 23 actions API key available

Transistor website Platform Documentation Capability data verified 2026-08-28

A membership lapses or a refund posts in the billing system

Agent reads the member's email address and their standing on the private show

List Subscribers confirms whether that person ever activated their personal feed

Agent separates genuine churn from a payment retry that is still in flight

Agent posts the proposed cut list with each member's activation state and tenure

The membership owner confirms which access ends, because a replacement feed URL cannot restore the old one

What This Integration Enables

Transistor hosts podcasts, but the operation that makes it interesting to an automation platform is the private one. A private podcast subscriber is a paying member whose access is a personal feed URL, delivered by email and pasted into whatever app they listen in. That makes membership and distribution the same object, and it makes the boundary between correcting a record and cutting off a listener a real, load bearing distinction. Transistor drew that line itself: Update Subscriber changes an email address while keeping the feed and the activation state, and Delete Subscriber revokes access immediately.

The public side is just as opinionated. Create Episode always produces a draft and never publishes, so a flow that stops there has an episode nobody can hear and no error saying so. Publish Episode is the only operation that changes publishing state, and a scheduled time is read in the show's own time zone rather than UTC. FlowRunner agents work that whole lifecycle, upload audio, write metadata, publish or schedule, manage private subscribers, pull per-episode analytics, and react to Transistor events in real time. The connectors handle the mechanics. The moments that reach a paying listener are where a person belongs.

Without FlowRunner

Publishing is a manual sequence Someone uploads the file, fills the metadata, and remembers to hit publish

Private access reconciled by spreadsheet Membership and podcast subscribers drift apart until an audit catches it

Analytics pulled per show, per window Three different reports with three different default ranges get compared as though they match

With FlowRunner

Publishing is a checked pipeline Audio, metadata, and transcript land first, and the feed write is its own deliberate step

Private access follows the membership A billing event moves a subscriber, and the activation state is part of the record

Analytics pulled on stated windows Every report is requested with explicit dates so the numbers are actually comparable

Use Case Scenarios

An episode assembled everywhere except the feed

A finished cut lands in Dropbox or on S3. The agent moves it into Transistor, either by handing over a public URL or, when the source is not publicly reachable, by running Upload Audio From URL to do the presigned exchange in one call. It calls Create Episode with the title, show notes, and season and episode numbers pulled from the production row in Notion, then stops. Everything is in place and nothing is audible, which is the correct state for a draft. The publish decision, including the scheduled time and the fact that Transistor reads it in the show's time zone, goes to the producer.

Private podcast access that tracks the membership

A subscription starts in Stripe or Chargebee. The agent calls Create Subscriber on the private show, which by default emails the new member their subscribing instructions. For an imported cohort it uses Create Subscribers In Batch instead, since the single create shares a rate limit with every other call. Later it runs List Subscribers with the activation filter to find members who were added but never opened their feed, and nudges exactly those people through Mailchimp rather than mailing the whole list again.

A sponsorship report that compares like with like

At the end of a flight, the agent pulls Get Show Analytics for the campaign window and Get All Episode Analytics for the same dates, always passing both dates explicitly, because the show and all-episode reports use different default windows and are not comparable otherwise. It joins the daily download counts against the episodes that carried the read, writes the result into Google Sheets, and posts the summary to the sales channel in Slack with the exact date range stated on the sheet.

Human-in-Loop Highlight

Delete Subscriber is the only operation on this connector that takes something away from a person who paid for it. It removes a private podcast subscriber and their personal feed URL stops working immediately, mid-episode if that is when the flow ran. What makes it a decision rather than a cleanup is that it cannot be walked back: re-adding the same person mints a new feed URL, so the member has to find the new email, delete the dead feed from their app, and subscribe again. Transistor makes the distinction explicit by giving corrections their own operation, since Update Subscriber changes an email while keeping the feed and activation intact. So a churn sync never deletes on its own. The agent posts: "4 memberships went past due overnight. 3 are hard cancellations. 1 is a card retry scheduled for tomorrow, and that member activated their feed 14 months ago. Confirm the 3, or hold all 4 until the retry settles." The membership owner answers, and only then does the agent call Delete Subscriber on the names they approved. The reconciliation was automatic. Cutting off a listener was not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

23 actions

Account

Get Authenticated User Reads the account the API key belongs to. The cheapest connection test, since it needs no show and no other id, and it confirms both that the key is valid and which account it reaches.

Shows

List Shows Lists the podcasts on the account, most recently updated first, with paging and an optional search. A show id or slug is what almost every other operation needs.
Get Show Reads one podcast, including its feed URL, artwork, categories, and episode count. Both an id and a slug work here.
Update Show Updates a podcast's metadata: title, description, author, artwork, categories, language, time zone, and publishing type. Only the fields sent are changed, and category and language are strict enumerations.

Episodes

List Episodes Lists a show's episodes with filters for publishing status and a search query. A draft episode is invisible to listeners but still appears here, so reconciling against a feed means filtering on published.
Get Episode Reads one episode in full, including its media URL, duration, share URL, transcript, and publishing state.
Create Episode Creates an episode on a show, always as a draft. This endpoint never publishes, so a flow that stops here has an episode nobody can hear and no error to say so.
Update Episode Updates an existing episode's metadata or replaces its audio. Only the fields sent are changed, and it cannot publish or unpublish.
Publish Episode Publishes an episode now or in the past, schedules it for the future, or reverts it to a draft. The only operation that changes publishing state. A scheduled time is read in the show's time zone, so changing that zone moves everything already scheduled.
Authorize Audio Upload Requests a presigned URL for uploading a large audio or video file and returns the audio URL to set on an episode afterward. The presigned URL expires quickly and the upload has to carry the exact content type named in the response.
Upload Audio From URL Copies an audio or video file from any URL the flow can reach into Transistor storage and returns the audio URL. Use it only when the source is not publicly reachable, since Transistor will fetch a public URL itself.

Analytics

Get Show Analytics Returns downloads per day for a whole podcast, defaulting to a two week window. The dates use a different format from the rest of the API, and both are required or neither.
Get All Episode Analytics Returns downloads per day broken down by episode for a whole podcast. Its default window is shorter than the other two reports, so the three are not comparable unless the dates are stated.
Get Episode Analytics Returns downloads per day for a single episode.

Private Subscribers

List Subscribers Lists the subscribers of a private podcast, with an optional search and an activation filter. The activation filter finds people who were added but never opened their feed, which is what a nudge campaign wants.
Get Subscriber Reads one private podcast subscriber, including their personal feed URL and whether they have activated it.
Create Subscriber Adds one subscriber to a private podcast and by default emails them the subscribing instructions. Suppressing that email leaves the subscriber with access but no idea how to use it.
Create Subscribers In Batch Adds several subscribers in one request. The right operation for importing a list, since the single create shares a rate limit with every other call.
Update Subscriber Changes a subscriber's email address while keeping their feed and activation state. A correction rather than a re-invitation.
Delete Subscriber Removes a private podcast subscriber and revokes their access, by id or by email and show. Their personal feed URL stops working immediately. The operation this page's human gate exists for.

Webhooks

List Webhooks Lists the webhook subscriptions on a show, including any the trigger created, which is how orphaned subscriptions from a deleted flow are found.
Create Webhook Subscribes an endpoint to one event on one show. A subscription covers exactly one event name and one show, so watching several events across several shows means several subscriptions.
Delete Webhook Unsubscribes a webhook so Transistor stops delivering to it. It does not touch the subscriptions the trigger manages.

Triggers

1 triggers

Event Triggers

On Transistor Event Fires when an episode is created or published, or when a private podcast subscriber is added or removed. Transistor subscribes one event per webhook, so selecting all events creates four subscriptions rather than one.

Frequently Asked Questions

What can FlowRunner do with Transistor?

FlowRunner agents can run Get Authenticated User, List Shows, and Get Show in Transistor, plus 20 more actions.

Does connecting Transistor to FlowRunner require OAuth?

No. Transistor connects to FlowRunner with an API key, no OAuth flow required.

Can Transistor trigger a FlowRunner workflow automatically?

Yes. Transistor supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Transistor

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us