SoundCloud Charts, Search & Artist Catalog Scraper: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "lofi"
  ],
  "searchType": "tracks",
  "chartGenre": "all",
  "sortBy": "relevance",
  "minPlayCount": 0,
  "minLikeCount": 0,
  "includeTracks": true,
  "includeAlbums": false,
  "includePlaylists": false,
  "includeTopTracks": false,
  "includeWebProfiles": false,
  "includePlaylistTracks": true,
  "includeUserProfile": true,
  "commentsSort": "newest",
  "relationship": "followers",
  "resolveStreamUrls": true,
  "maxItems": 2
}

---
name: soundcloud-charts-search-and-artist-catalog
description: "SoundCloud tracks, artists, playlists, albums and comments - charts, search results, full artist catalogs, playlist contents, engagement metrics, creator details, artwork, waveform and stream metadata. Runs the Apify Actor nimbryxo-studio/soundcloud-charts-search-and-artist-catalog. Use when the user needs SoundCloud data with fields such as recordType, title, artist, playCount, likeCount, genre and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/soundcloud-charts-search-and-artist-catalog"
  store-url: "https://apify.com/nimbryxo-studio/soundcloud-charts-search-and-artist-catalog"
---

# SoundCloud Charts, Search & Artist Catalog Scraper

Use this skill to fetch SoundCloud data with the Apify Actor `nimbryxo-studio/soundcloud-charts-search-and-artist-catalog` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `charts`, `artistTracks`, `byUrl`, `comments`, `followers`, required | Choose the intent. Keyword search, New & Hot charts, an artist catalog, specific URLs, track comments, or an artist's followers. |
| `searchQueries` | array | One or more keywords or artist names (mode=search). Example: lofi, techno, ambient jazz. |
| `searchType` | one of `tracks`, `users`, `playlists`, `albums`, `all` | What kind of results to return (mode=search). |
| `chartGenre` | string | Global New & Hot returns up to 100 tracks. Genre values use SoundCloud's current trending-by-genre lists (about 50 tracks each). |
| `searchGenre` | string | Optional SoundCloud genre filter for track and playlist searches. Leave as any genre to search everything. This is a real SoundCloud filter, not a client-side guess. |
| `sortBy` | one of `relevance`, `newest`, `mostPlayed`, `mostLiked` | How to order the rows already fetched. SoundCloud search itself is relevance-ordered, so this is a client-side sort of that result set. |
| `minPlayCount` | integer | Drop track/playlist rows below this play count after fetching. 0 means no filter. |
| `minLikeCount` | integer | Drop track/playlist rows below this like count after fetching. 0 means no filter. |
| `artistUrls` | array | Artist profile URLs, usernames, or numeric user IDs. Used by artistTracks and followers modes. |
| `includeTracks` | boolean | Include the artist's uploaded tracks. |
| `includeAlbums` | boolean | Include the artist's albums/EPs as playlist rows. |
| `includePlaylists` | boolean | Include the artist's playlists as playlist rows. |
| `includeTopTracks` | boolean | Include SoundCloud's small top-tracks list for each artist. |
| `includeWebProfiles` | boolean | Add the artist's public social/web profile links to the profile row. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQueries": [
    "lofi"
  ],
  "searchType": "tracks",
  "chartGenre": "all",
  "sortBy": "relevance",
  "minPlayCount": 0,
  "minLikeCount": 0,
  "includeTracks": true,
  "includeAlbums": false,
  "includePlaylists": false,
  "includeTopTracks": false,
  "includeWebProfiles": false,
  "includePlaylistTracks": true,
  "includeUserProfile": true,
  "commentsSort": "newest",
  "relationship": "followers",
  "resolveStreamUrls": true,
  "maxItems": 2
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~soundcloud-charts-search-and-artist-catalog/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~soundcloud-charts-search-and-artist-catalog/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `recordType`, `title`, `artist`, `playCount`, `likeCount`, `genre`, `uploadDate`, `url`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.