--- title: "SoundCloud Integration" description: "Connect AI agents to SoundCloud. Agents search the public track catalog, manage uploaded tracks and their visibility, build and populate playlists, and curate the connected account's liked tracks." url: https://flowrunner.ai/integrations/soundcloud date_modified: 2026-08-01T02:40:32-07:00 --- # SoundCloud [Social Media](https://flowrunner.ai/integrations/category/marketing-social) Connect AI agents to SoundCloud. Agents search the public track catalog, manage uploaded tracks and their visibility, build and populate playlists, and curate the connected account's liked tracks. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · OAuth · available [SoundCloud website](https://soundcloud.com/) · [Platform Documentation](https://developers.soundcloud.com/docs/api/guide) · Capability data verified 2026-08-12 1. Release day arrives for a track that has been sitting private since the master was uploaded 2. List My Tracks locates the track and Get Track confirms its metadata and current private sharing status 3. The agent verifies the release checklist: title matches the announcement copy, description carries the credits and links, artwork is in place 4. The label manager gives the go, confirming this exact track goes public at this exact time 5. Update Track flips sharing to public, and the track is live 6. The permalink flows into the announcement systems: the blog post, the team channel, the release tracker 7. The release announcement posts everywhere at once, minutes after the flip, while the algorithm window is freshest ## What This Integration Enables For a label, a podcast network, or any team running a catalog on SoundCloud, the platform work around the music is pure operations: metadata hygiene, visibility management, playlist curation, and the reporting that says what is working. This connector hands that work to agents. FlowRunner agents search the public catalog by keyword and genre, manage the connected account's uploaded tracks and their public or private visibility, build playlists from search results or the library, and curate likes, with everything syncable to sheets, CMSs, and channels. The stance: the moment of publication deserves ceremony, and everything around it deserves none. Automate the sweep, the sync, and the assembly; put a person on the flip. - Discover tracks by keyword and genre for curation and content pipelines - Manage uploaded tracks: titles, descriptions, and public or private visibility - Assemble playlists from search results or your own library in one pass - Log catalog and engagement metadata into spreadsheets on schedule - Feed track metadata into blogs, announcements, and release trackers ### Without FlowRunner **Release day is a checklist of tabs**: Publishing means flipping visibility, copying permalinks, posting announcements, and updating trackers by hand, in order, under time pressure **Catalog stats live in the app**: Play and like counts get checked track by track when someone wonders, and trends go unnoticed **Playlists curated when there is time**: The genre playlists that drive discovery go stale because assembling them is an evening of searching ### With FlowRunner **Release day is one approval**: The agent stages everything, a person says go, and visibility, announcements, and trackers update in one coordinated pass **The catalog reports itself**: Track metadata and engagement counts sweep into a spreadsheet on schedule, and movement stands out **Curation as a running flow**: Search-driven playlists rebuild themselves from keyword and genre queries, reviewed before they publish ## Use Case Scenarios ### The catalog report that catches the breakout Nightly, List My Tracks pages through the account's uploads and appends each track's play and like counts to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The agent computes deltas against yesterday and posts anything moving unusually fast to [Slack](https://flowrunner.ai/integrations/slack). When a two-year-old track suddenly triples its daily plays because a creator used it somewhere, the team finds out that morning, while there is still a moment to ride. ### Release publishing as a single coordinated event The full release flow from the primary workflow, staged metadata check, human go, Update Track to public, runs its final act automatically: Get Track pulls the fresh permalink, [WordPress](https://flowrunner.ai/integrations/wordpress) publishes the embed-ready release post, and the announcement lands in the team channel. Because one flow owns the sequence, the blog never links a track that is still private and the announcement never goes out before the track does. ### The genre playlist that stays alive A weekly flow runs Search Tracks for the playlist's defining keywords and genre filter, scores candidates on recency and engagement, and drafts an updated track list. The curator reviews the draft, cuts what does not fit the brand, and approves. Create Playlist publishes the new set with the approved order. Discovery playlists stop being a good intention and become a standing output, with taste applied exactly where taste matters. ## Human-in-Loop Highlight Update Track carries a one-word field with outsized consequences: sharing. Flipping a track from private to public releases it to the world, and if the flip happens early, the wrong track, the wrong day, an unfinished master, the release is simply out. Listeners heard it, rippers ripped it, and setting it back to private un-publishes nothing that matters. Labels have lost release-day momentum to exactly this mistake. So in FlowRunner release flows, visibility changes are the one edit that never runs on schedule alone: the agent stages the track, verifies metadata against the release checklist, and holds at a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step until the label manager confirms this track, this moment. Title and description edits on already-public tracks flow freely, and private-direction flips, pulling something back, run immediately on request because speed helps there. The gate points one way: into public, with a person's name on the go. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Account 1 - **Get Current User** Retrieves the profile of the connected SoundCloud account: username, display name, follower and track counts, and public profile URL. The identity check before operations run. ### Tracks 4 - **Search Tracks** Searches SoundCloud's public catalog by keyword, returning tracks with title, artist, duration, play count, and stream and permalink URLs. Supports a result limit up to 200 and optional genre filtering. - **Get Track** Retrieves full metadata for a single track by numeric ID: title, description, sharing status, duration, genre, tags, play and like counts, and the owning user. The inspection step before updates and likes. - **List My Tracks** Lists the connected account's uploaded tracks, most recent first, with each track's metadata and engagement counts. Uses linked partitioning; pass the returned cursor to page large libraries. - **Update Track** Updates a track owned by the connected account: title, description, and public or private sharing. Only provided fields change. The visibility flip this page's human gate governs. ### Playlists 2 - **List My Playlists** Lists the account's playlists with title, description, sharing status, track count, and public URL. Cursor-paged via linked partitioning. - **Create Playlist** Creates a new playlist with a title, visibility, and an optional ordered list of track IDs sourced from Search Tracks, Get Track, or List My Tracks. ### Likes 2 - **List Liked Tracks** Lists the account's liked tracks, most recent first, with title, artist, duration, and engagement counts. Cursor-paged. - **Like Track** Adds a track to the account's likes by numeric ID. Idempotent: liking an already-liked track succeeds without error. ## Frequently Asked Questions ### What can FlowRunner do with SoundCloud? FlowRunner agents can run Get Current User, Search Tracks, and Get Track in SoundCloud, plus 6 more actions. ### Does connecting SoundCloud to FlowRunner require OAuth? Yes. SoundCloud connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can SoundCloud trigger a FlowRunner workflow automatically? SoundCloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SoundCloud?** This integration exposes SoundCloud to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/soundcloud. Site index: https://flowrunner.ai/llms.txt