Beatoven.ai
AIGenerate royalty-free, commercially licensed background music from a text prompt with Beatoven.ai. Agents score videos, podcasts, and product demos without a licensing negotiation.
What This Integration Enables
The interesting thing about Beatoven.ai is not that software wrote the music. It is that the output is cleared for commercial use, which turns a legal question into a workflow step. Most background music problems are licensing problems wearing a creative costume: the track sounds fine, but nobody can say with confidence what happens when the client runs it as a paid ad in three countries. This connector removes that argument from the critical path.
An agent describes what it needs in plain language, and Compose Track starts an asynchronous composition that returns a task ID. Polling Get Composition Status until it reports Composed yields hosted URLs for the full track and for each separated stem, which the next step can download, attach, or hand to an editor. Tracks can be initialized and kept under a project, re-rendered later at a different length or looping style, and revised by describing the change rather than opening a session. There is also a Search Music path that queries an existing catalog rather than generating anything, and the difference between those two paths is precisely where a person belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Scoring a client cut on delivery
An agency finishes a thirty second product spot. The project record already carries a mood brief and the exact runtime. The agent turns the brief into a composition prompt, calls Compose Track, and polls Get Composition Status until the track is ready. It archives the full track and the four stems to Google Drive in the client folder, then posts the stem URLs into Slack with the prompt attached so the editor can see what was asked for. If the editor wants a change, they type it as a sentence and the agent runs Edit Track against that version rather than starting over.
Looping beds that get re-cut without a new brief
An app needs ambient audio for its waiting state and the required length keeps changing as the product team adjusts the flow. The agent uses Create Track once to register the track under the project, then calls Compose Existing Track whenever a new length or looping style is needed. Version history stays on the same track ID, so every variant traces back to a single approved brief rather than becoming an untracked new asset.
Generation spend visible before the invoice
Composition consumes account allowance, and a busy production month can move faster than anyone's mental accounting. A scheduled flow calls Get Usage on a daily grain, writes the numbers into a tracking record, and alerts the producer in Slack when consumption crosses the threshold they set for the month. Get Account confirms which account generated a given track, which matters when several client projects share one key.
Human-in-Loop Highlight
The gate here is provenance, and it exists because this connector offers two paths that produce interchangeable-sounding results with different footing underneath them. Compose Track generates new music that is cleared for commercial use. Search Music returns matches from an existing catalog, which is a library lookup rather than a generation, and its terms are a separate question. A flow that quietly falls back from generation to catalog search when a composition times out has just changed what is going into a paid client asset without telling anyone.
So the agent does not make that substitution on its own. When generation fails or the composition does not come back in time, it stops and posts to the producer in Slack: "Compose Track for the Northfield spot failed after two attempts. I found three catalog matches for the same brief. Do you want to retry generation, or clear one of these catalog tracks for the client cut? I will not attach a catalog track to a deliverable without your answer." The producer decides, and the record of which path was taken stays attached to the asset. That answer is worth having before the spot runs, not after somebody asks for the license.
Agent Capabilities
10 actionsComposition
4- Compose Track Start an asynchronous composition from a natural language prompt describing mood, genre, instrumentation, and length. Returns a task ID immediately; poll Get Composition Status until the status is Composed to collect the finished track and its stems. Generated music is cleared for commercial use.
- Compose Existing Track Start a composition for a track already initialized with Create Track, optionally overriding its prompt. This is how you re-render at a different length or looping style while keeping the same track ID and version history. Returns a task ID to poll.
- Edit Track Request a revision of an already composed track by describing the change in plain language, targeting a specific track version. Starts a new asynchronous task, so poll Get Composition Status with the returned task ID to collect the revised audio. This is what turns editor feedback into a call rather than a session.
- Get Composition Status Retrieve the progress of a composition task through Composing, Running, and Composed. Once the status is Composed, the response carries hosted URLs for the full track and for each separated stem covering bass, chords, melody, and percussion.
Track Management
3- Create Track Initialize a track record from a prompt without composing audio yet, returning the new track ID. Used when the track needs to live under a project, when several alternatives are wanted up front, or when the same track will be re-composed later.
- Get Track Retrieve a single track by identifier, including the prompt it came from, its tempo, duration, structure, and the hosted URLs of the composed audio and stems. Pass a version number to inspect an earlier revision.
- List Tracks Return the tracks belonging to the authenticated account, so a flow can inventory previously generated music or pick up a track ID for a later compose or edit call.
Catalog Search
1- Search Music Run a semantic search over a Beatoven.ai music catalog using a natural language query, with a configurable result count and a filter expression for catalog metadata. This searches an existing library rather than generating new audio, which is why it belongs behind an approval when the result is destined for a customer facing asset.
Account
2- Get Account Retrieve the profile behind the configured API key, including the associated email and the API call allowance. Useful as a connection check at the start of a flow, or to confirm which account generated a given track when several projects share credentials.
- Get Usage Return API consumption for the account aggregated over a time grain, defaulting to daily buckets. Used to alert on spend or to log consumption on a schedule before it turns into a surprise.
Frequently Asked Questions
What can FlowRunner do with Beatoven.ai?
FlowRunner agents can run Compose Track, Get Composition Status, and Create Track in Beatoven.ai, plus 7 more actions.
Does connecting Beatoven.ai to FlowRunner require OAuth?
No. Beatoven.ai connects to FlowRunner with an API key, no OAuth flow required.
Can Beatoven.ai trigger a FlowRunner workflow automatically?
Beatoven.ai doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Beatoven.ai
$100 in credits. No card required. Connect in minutes.