How to Connect TrackTag to Zapier
Updated August 8, 2026·6 min read·by the TrackTag team
TrackTag is listed in Zapier's public app directory, so you can connect it to Google Sheets, Dropbox, Airtable, Notion, Slack, Gmail and thousands of other apps without writing any code. This page covers what the integration does, how to set it up, every field you can map, what it costs in credits and what to do when something goes wrong.
What the TrackTag integration gives you
The app has three pieces you can use in any combination:
- •Trigger, "Analysis Finished": fires the moment a TrackTag analysis completes, carrying BPM, key, genres, mood, instruments and the description as separate fields
- •Action, "Analyze Track": send an audio file URL to TrackTag from any Zap
- •Search, "Get Analysis": look up a finished analysis later by its ID
The trigger fires for work you do in Studio
This is the part most people miss. "Analysis Finished" does not only fire for tracks a Zap sent in. Every track you analyze normally in TrackTag Studio fires it too, so you can keep working exactly as you do now and have a Zap file every result into a spreadsheet, a Notion database or a Slack channel behind you.
Each event carries an Origin field holding either studio or api. Add a Zapier filter on it when a Zap should react only to in-app batches, or only to API calls.
Connecting your account
Setup takes a couple of minutes and works on any Zapier plan, including the free one:
- •1. In TrackTag, open Studio and go to the Integrations tab (API, MCP and Zapier)
- •2. Create an API key and copy it
- •3. In Zapier, search for TrackTag and add a TrackTag step to a Zap
- •4. When Zapier asks to connect an account, paste the key
Build it for free with a test key
Keys starting with tt_test_ never spend credits. They return a canned sample result whose field shapes match live responses exactly, so you can build and test an entire Zap without paying for a single analysis. When the Zap works, swap in your tt_live_ key: nothing else about the Zap has to change.
Every field you can map
Results arrive flattened, so you map one field per spreadsheet column instead of digging through nested data. Alongside the raw fields (BPM, Key, Genres, Mood, Instruments, Description, Energy, Valence, Danceability, Meter, Model, Credits charged, Origin) there are three ready made ones that save you laying anything out:
- •Summary line: "Midnight Drive.mp3, 122 BPM, A minor, deep house", which makes a good email subject or Slack message
- •Full report (plain text): the whole tag set laid out, ready to paste into a message or a Notion page
- •Full report (HTML): a designed version for email steps, which renders properly in Gmail and Outlook
What it costs
Zaps spend the same credits as everything else in TrackTag: 1 credit per track on Core (9 fields including tags), 2 on Ultra (all 35 fields, including the written description). There is no separate Zapier plan or fee on our side, and analyses that fail are refunded automatically.
Troubleshooting
Nearly every problem people hit is one of these:
- •"Download failed" or an HTML page analyzed instead of audio: the Audio file URL must return the file itself. In Dropbox triggers use the Direct Media Link field, in Google Drive use the download URL. Files up to 60 MB.
- •The action times out on long files: turn off "Wait for the result". Zapier stops a step after about 30 seconds, so read the result from the "Analysis Finished" trigger instead.
- •"Out of credits": the step errors without charging you. Top up and the Zap runs again.
- •Zapier asks you to reconnect: the API key was revoked or replaced. Create a new one in Studio and reconnect the account.
- •A failed analysis: credits are refunded automatically. Switch on "Also trigger on failed analyses" in the trigger if you want to be notified when it happens.
- •Signing in to Zapier from the TrackTag desktop app does nothing: the desktop app opens links in your default browser, so Zapier cannot hand the session back. Build your Zaps at tracktag.me in a browser, or on zapier.com. The Zaps themselves work the same either way.
Getting help
For questions about Zaps themselves, or anything happening on Zapier's side, contact Zapier support at zapier.com/app/get-help: they have the full context on your Zap history and pass real bugs straight to us. For questions about TrackTag, credits or your API key, contact us at tracktag.me/support.
Tag your whole catalog with AI
BPM, key, genre, moods, instruments and keywords: 35+ fields per track, exported ready for libraries.
Open TrackTag Studio →Frequently asked questions
Do I need a paid Zapier plan to use TrackTag?
No. TrackTag works on any Zapier plan, including the free one. A two step Zap (for example, Analysis Finished into Google Sheets) runs on the free plan; Zapier itself requires a paid plan only once a Zap has three or more steps.
Does a Zap fire when I analyze tracks in TrackTag Studio?
Yes. The "Analysis Finished" trigger fires for analyses you run in Studio as well as ones started by a Zap or the API. Each event carries an Origin field (studio or api) you can filter on.
How much does a Zap cost in credits?
The same as anywhere else in TrackTag: 1 credit per track on Core, 2 on Ultra. Failed analyses are refunded automatically, and test keys (tt_test_) never spend credits at all.
Why does TrackTag say it cannot download my file?
The Audio file URL has to return the audio itself, not a preview page. In Dropbox pick the Direct Media Link field rather than the plain Link field, and in Google Drive use the download URL. The limit is 60 MB per file.
Can I build a Zap without spending credits?
Yes. Create a test key (it starts with tt_test_) in Studio and connect that. It returns a sample result with identical field shapes, so every mapping you build stays correct when you switch to your live key.