Audio Analysis API for New Music Bounces

October 30, 2026·by TrackTag team

If you need an audio analysis API to tag new music bounces as they arrive, the key is to connect the folder event to analysis and then send the results somewhere your team can review them. For a shared cloud folder, you can build that workflow with Dropbox, Zapier, TrackTag, and Google Sheets. For a local folder, TrackTag Studio can index files and show which ones are still untagged, while a separate watcher using the public API can handle hands-off processing.

One important distinction: TrackTag does not claim to continuously watch a local folder and start analysis by itself. Its local library scan identifies files and gives you an Analyze untagged action. Cloud folder triggers in Zapier, or a separate file-watcher you build around the API, are the ways to automate new arrivals.

Choose where your bounces land

Start by deciding whether the folder is local or cloud-based. That choice determines how the workflow detects a new file.

Shared Dropbox folder: use Zapier

This is the easiest option when producers, artists, or clients deliver bounces to a shared folder. A Zap can start when a new file appears in Dropbox, send the audio to TrackTag, and then record the returned analysis in Sheets, Airtable, or Notion. You can also send a Slack message when a track is ready for review.

TrackTag’s Zapier app includes an Analyze Track action and an Analysis Finished trigger. Zapier also lists a workflow for analyzing new files in Google Drive folders with TrackTag, showing the same basic pattern: detect an upload, analyze it, and use the returned results. (zapier.com)

Local bounce folder: use My Library or an API watcher

If you bounce directly to a computer folder, TrackTag Studio batch audio analyzer can connect to a local music folder and index its files. The scan reads file names and sizes on your machine. Nothing is uploaded until you explicitly analyze a track. The library marks files as Tagged or Untagged, and you can sort the list and analyze the untagged backlog.

That workflow is useful for a deliberate review pass, but it is not an automatic file-arrival trigger. If every new bounce must be processed without opening Studio, you need a separate local watcher that detects completed files and submits them to the TrackTag public API.

Build a Dropbox to Sheets workflow in Zapier

Use this setup when you want every incoming bounce analyzed and logged without writing code. The exact labels in Zapier can vary slightly by app version, but the workflow logic stays the same.

1. Create an incoming folder. In Dropbox, make a dedicated folder such as Incoming Bounces. Ask collaborators to put new audio there, rather than in a folder containing approved masters or old versions.

2. Start a Zap with a new-file trigger. Choose Dropbox’s new-file-in-folder trigger and select Incoming Bounces. If your team uses subfolders, decide whether they should also be monitored. Keeping the intake folder simple makes testing easier.

3. Add a file filter. Continue only for audio formats your team intends to analyze. For example, you might accept WAV, AIFF, FLAC, or MP3 files and exclude PDFs, artwork, and text notes. Confirm the actual file type values Zapier receives with a test upload before relying on the filter.

4. Send the audio to TrackTag. Add TrackTag’s Analyze Track action and map the Dropbox file or file URL required by the action. Test with a short bounce first. Check that TrackTag receives the audio itself, not just a Dropbox preview or sharing page that it cannot use as an audio file.

5. Choose the analysis level. Select Core when you need the key fields that help file and find a track. Choose Ultra when your review needs all 35 fields, including a full description, themes, occasions, structure, and production or mixing notes. Both levels use the same engine on the same audio, so the level changes how much information you receive, not the analysis quality.

6. Create a row in Google Sheets. Map the original file name and folder alongside useful results such as BPM, key, genres, subgenres, moods, emotions, themes, instruments, and vocals. Include a status column such as Needs review so the sheet is a queue, not just a dump of metadata.

7. Test and publish. Upload a new test bounce, confirm the analysis fields appear in the expected columns, and check how the workflow behaves when the file is unsupported or the analysis does not complete. Then publish the Zap and monitor the first few real deliveries.

For exact setup details on the TrackTag app in Zapier, use the TrackTag Zapier connection guide. TrackTag also supports Dropbox, Google Sheets, Airtable, Notion, and Slack through Zapier, so you can send completed analysis to a database or notify the people responsible for review.

Make the folder workflow reliable

A new-file event can happen while a large audio file is still uploading. Avoid sending a partial bounce to analysis. If your automation platform allows a delay or a retry, use it before the TrackTag action, then test with a large file. An even safer handoff is to upload to a temporary folder first and move the finished file into Incoming Bounces only after the upload completes.

Give each bounce a stable identifier. A useful combination is the file name plus the Dropbox file ID or another unique delivery ID. Keep that value in your tracking sheet or database. It helps your team spot duplicate uploads and compare results when a producer replaces a bounce with a revised version.

Set expectations for revisions. If a file is replaced, decide whether to analyze it again or preserve the first result for comparison. A clear naming convention can help, such as Artist_Title_Mix_03.wav, but a changed file name alone is not a reliable signal that it is a new musical version. Keep the original delivery date and version label in your tracking record.

Do not treat every returned field as approved release metadata. A useful workflow records analysis first, then gives a human a place to confirm tags before delivery. For example, a sync library may review themes, moods, instruments, and production notes, while a label’s intake team may prioritize genre, key, BPM, vocals, and version name.

Use the API for a local watch folder

If your bounce destination must stay on a local drive or shared server, build a small watcher that calls TrackTag’s public API. The API accepts a track and returns the same analysis as JSON. It uses the same credit balance as Studio, with default limits of 10 requests per minute and 2,000 analyses per day per key.

A dependable watcher should follow this sequence:

1. Monitor one designated intake folder, not the entire catalog.

2. When a new file appears, wait until its size stops changing. This avoids submitting a file that is still being copied.

3. Add the file to a queue and record its path, size, modification time, and processing status.

4. Submit the track using the request format and authentication instructions in the TrackTag API documentation.

5. Save the returned JSON beside a record of the file, or pass selected values to your own database.

6. Mark successful files as complete, and retry failed submissions with a limit so one bad file does not loop indefinitely.

7. Respect the per-key request limit. At 10 requests per minute, a queue should pace requests rather than launching a large batch all at once.

Keep the watcher’s credentials out of shared scripts and public folders. Create and manage API keys in TrackTag Studio, and test the watcher with a few files before pointing it at a high-volume delivery folder. The API is intended for workflows such as enriching label deliveries or showing analysis in another tool, while Zapier is the no-code route for common cloud handoffs.

Pick fields and credits before you scale

Choose the output based on what the receiving team will actually use. Core costs 1 credit per track and returns 9 fields, including keyword tags. Ultra costs 2 credits and returns all 35 fields, including the written description. You can analyze a track with Core and later use the 1-credit difference to re-analyze it at Ultra if a more detailed brief is needed.

For example, if a label receives 200 new bounces and only needs searchable tags, Core uses 200 credits. If the sync team needs themes, occasions, structure, and descriptions for every submission, Ultra uses 400 credits. The analysis level does not make a track more or less accurately analyzed, it determines how much of the result is returned.

TrackTag starts with free credits, then offers one-time credit packs rather than requiring a subscription. That can suit a label with irregular delivery volume. If you process new music continuously, compare your expected monthly track count with the available plan options before choosing how to run the automation.

For a broader backlog rather than a live intake workflow, see the guide to batch tagging music files. You can also export results from TrackTag Studio as CSV or Excel, JSON, XML, Markdown, TXT, or PDF, including a whole batch, a selected subset, or one file per track.

Where MCP and the desktop app fit

The MCP server is useful when you want to ask Claude Desktop, Cursor, or Claude Code to analyze a track, search your local audio files by name, or check your credit balance from inside a conversation. It runs on your machine, but it is not a substitute for a folder-arrival trigger. Use Zapier or a purpose-built watcher when new files must be processed automatically.

The Mac and Windows desktop app is a good fit when your team uses TrackTag’s local library view for ongoing catalog work. Connected folders stay connected without repeated browser permission prompts, and long batches run in their own window. The browser folder scan works in Chrome, Edge, and Brave; Safari and Firefox do not support that folder access.

FAQ

Can TrackTag automatically watch a local folder?

TrackTag Studio can index a local folder, show Tagged and Untagged files, and analyze the untagged backlog. It does not itself claim to automatically start analysis whenever a new local file arrives. For that behavior, connect a watcher you control to the public API.

How do I use a music analysis API when a bounce arrives in Dropbox?

Create a Zap with a Dropbox new-file trigger, add TrackTag’s Analyze Track action, and send the returned fields to Sheets, Airtable, or another destination. Test that Zapier passes an audio file TrackTag can access, not just a preview page.

Is an audio analyzer API useful for a label delivery folder?

Yes, if you want new deliveries to produce structured fields without manually opening each file. Store the original file identity, analysis results, and review status together so your team can distinguish a fresh bounce from a duplicate or revision.

Should I use Core or Ultra for new bounces?

Use Core for the 9 searchable fields when your workflow mainly needs to file and find tracks. Use Ultra when reviewers need all 35 fields, including descriptions, themes, occasions, and production notes. Both use the same analysis engine, and a Core result can later be upgraded to Ultra for 1 additional credit.

Tag your whole catalog with AI

BPM, key, genre, moods, instruments and keywords: 30+ fields per track, exported ready for libraries.

Open TrackTag Studio →

← All posts·In-depth guides