Breakdance Integration

Connect WPVoicer output to Breakdance page flows.

Publish audio-enabled articles in Breakdance while keeping the generation and account logic managed inside WPVoicer and the plugin.

How the Breakdance integration works

WPVoicer adds a dedicated Breakdance dynamic data provider, so the generated audio can be selected directly from Breakdance fields without exposing API configuration to the client. If intro/outro text is enabled in the plugin, it is already included in the MP3 that Breakdance receives.

Generate the post audio

Use WPVoicer inside WordPress to generate the MP3 for the article. The resulting media attachment is linked to that post.

Edit the Breakdance template

Open the article template or section where the listening experience should appear.

Choose WPVoicer dynamic data

In a URL-compatible field, select Dynamic Data -> WPVoicer -> Audio URL. Use Audio ID only for elements that need an attachment ID.

Design the front-end block

Breakdance controls the visual layer; WPVoicer supplies the correct MP3 for the current post.

Primary fieldAudio URL under the WPVoicer dynamic data group.
Optional fieldAudio ID when the component expects the Media Library attachment ID.
FallbackUse [wpvoicer_audio] in shortcode-capable content when you want the plugin-rendered player.
Technical note: the plugin registers a Breakdance dynamic data provider and resolves the audio from the current WordPress post context.

Post-level mapping

Associate generated MP3 with article pages in a predictable builder workflow.

No API overhead

The integration path stays plugin-native and avoids external setup complexity.

FAQ

Breakdance implementation questions.

How WPVoicer output appears inside Breakdance dynamic data fields.

Where is the audio field in Breakdance?

Select Dynamic Data -> WPVoicer -> Audio URL in a URL-compatible field.

What does the Audio URL field return?

It returns the generated MP3 URL attached to the current WordPress post.

Can Breakdance still control the design?

Yes. Breakdance controls the layout and visual presentation; WPVoicer only supplies the post-specific audio value.

What if a field does not support dynamic data?

Use [wpvoicer_audio] in shortcode-capable content as the fallback path.