Zapier
Connect Finetuning to 8,000+ apps — auto-generate music and route finished tracks anywhere, no code required
Connect Finetuning to 8,000+ apps with Zapier — automatically generate music and route finished tracks anywhere (Google Sheets, Gmail, Slack, Drive, Notion, Airtable, and more) without writing code.
Private beta. The Finetuning Zapier integration is currently in private beta. Use the invite link below to add it to your Zapier account.
Requirements
- A Finetuning Pro or Lifetime plan (API access is included on these plans).
- A Finetuning API key (see below).
- A free or paid Zapier account.
Step 1 — Get your API key
- Log in to finetuning.ai.
- Go to Settings → API Keys.
- Click Create API Key, give it a name (e.g.
Zapier), and copy the key. It starts withft_live_.
Keep this key secret — it can create music on your account. You can revoke it anytime from the same page.
Step 2 — Connect Finetuning in Zapier
- Open the invite link and accept it.
- In any Zap, search for Finetuning as your trigger or action app.
- When prompted to connect your account, paste your API key and continue. Zapier will confirm the connection and show your email + plan.
What you can do
⚡ Trigger — New Completed Track
Fires instantly the moment one of your tracks finishes generating — both music and instrumental tracks (they share one library). Each run gives you that one finished track.
Fields you get: Track ID, Status, Audio URL (MP3), Duration, Description, Tempo (BPM), Key & Scale, Created At, Completed At.
The trigger does not fire for sound effects — they live in their own library. Use the Delay + Find Sound Effect by ID pattern below instead.
Example Zaps
- New track → add a row to Google Sheets (build a library log)
- New track → email me the MP3 link via Gmail
- New track → post to a Slack/Discord channel
- New track → upload the MP3 to Google Drive / Dropbox
The trigger is push-based (instant) — there's no polling delay. Just make sure your Zap is turned on; the trigger only listens while the Zap is published.
🎵 Action — Create Music Track
Starts generating a new track from a text description. It returns the Track ID right away — it does not wait for the audio (music renders in the background on our GPUs, which takes longer than Zapier allows a single step to run).
Main field: Music Description (e.g. lofi chill piano, rainy night, mellow).
Optional: Lyrics, Duration (seconds), Tempo (BPM), Language, Time Signature, Musical Key, Scale.
To get the finished MP3 in the same Zap, add two steps after this one:
1. Finetuning — Create Music Track
2. Delay by Zapier — 1–2 minutes
3. Finetuning — Find Track by ID (pass the Track ID from step 1)
→ now you have the Audio URL…or, simpler: kick off the track however you like and use the New Completed Track trigger in a separate Zap to handle the finished file.
🎹 Action — Create Instrumental Track
Starts generating a vocal-free instrumental track from a text description. Like Create Music Track, it returns the Track ID right away while the audio renders in the background.
Main field: Music Description (e.g. warm lo-fi hip hop beat, dusty vinyl, mellow Rhodes piano).
Optional: Duration (default 120s, in 15-second steps from 30–210), Enhance Prompt (on by default — AI expands your description), Seed (reproduce a previous result).
There's no BPM, key, scale, or lyrics to set — the model handles the musical details from your description.
Instrumental tracks land in the same library as music tracks, so the same follow-ups work: Delay + Find Track by ID, or the New Completed Track trigger.
🔊 Action — Create Sound Effect
Starts generating a short sound effect (1–8 seconds) from a text description and returns the Sound Effect ID right away.
Main field: Sound Description (e.g. heavy wooden door creaking open, old hinges).
Optional: Duration (default 4s, in half-second steps from 1–8), Enhance Prompt.
Sound effects render fast — a 1-minute Delay is plenty. To get the finished MP3:
1. Finetuning — Create Sound Effect
2. Delay by Zapier — 1 minute
3. Finetuning — Find Sound Effect by ID (pass the Sound Effect ID from step 1)
→ now you have the Audio URLSound effects have a daily cap of 100 per day (shared with the web app). Every Create response includes Daily Generations Remaining.
🔎 Search — Find Track by ID
Looks up a single track (music or instrumental) by its ID. Returns the track even if it's still processing (the Audio URL will be blank until it's done), so it won't error if you run it too early. Pair it with a Delay step as shown above.
🔎 Search — Find Sound Effect by ID
The sound-effect counterpart of Find Track by ID — looks up one sound effect by its ID, even while it's still processing. This is the way to fetch a finished sound effect, since the New Completed Track trigger doesn't cover SFX.
Recommended patterns
| You want to… | Build this |
|---|---|
| Do something every time a track finishes | New Completed Track trigger → your action |
| Generate a track from another app's event and get the MP3 | Create Music Track → Delay → Find Track by ID |
| Generate a vocal-free instrumental and get the MP3 | Create Instrumental Track → Delay → Find Track by ID |
| Generate a sound effect and get the MP3 | Create Sound Effect → Delay (1 min) → Find Sound Effect by ID |
| Generate in bulk and collect results later | Create Music Track (many) + a separate New Completed Track Zap to catch them |
FAQ & troubleshooting
My Zap connected but nothing happens when a track finishes. Make sure the Zap is turned on / published. The instant trigger only listens while the Zap is live — testing in the editor alone won't catch real tracks.
The email/notification went to spam. For Gmail/Outlook steps, mark the message "Not spam" once or add the sender to your contacts. A more descriptive subject and body (not just a bare link) also helps deliverability.
The Create action didn't return an Audio URL. That's expected — every Create action returns immediately while the audio renders. Add a Delay + Find Track by ID step (or Find Sound Effect by ID for sound effects), or use the New Completed Track trigger for music/instrumental tracks.
Can I use this on the Free plan? No — API access (and therefore Zapier) requires a Pro or Lifetime plan.
Is there an "advanced webhook" field on Create? Yes, on all three Create actions — but most people should ignore it. It lets developers POST the finished audio to their own URL. For Zapier, the New Completed Track trigger (music/instrumental) or the Delay + Find pattern (sound effects) already handles delivery — leave the webhook field blank. (If you're building a custom backend instead of using Zapier, see Webhooks.)
Need help?
Contact Finetuning support and mention you're using the Zapier integration (beta). Include your Track ID(s) if a specific generation is involved.