Adding an audio version to your Kajabi content
Kajabi has no plugin directory, but audio still goes on without a developer. The custom code block, the feed and the API, step by step, and what the player leaves untouched.
Kajabi brings courses, membership areas, sales pages and, often, a blog or newsletter together on one platform. You build quickly, without writing code, and that is the whole point. The flip side is the same as on other builders of this kind: there is no plugin directory the way WordPress has one, so when you want a feature that is not built in, you add it through the front end rather than through an admin screen. Offering an audio version of your articles and pages falls into that category. The good news is that it takes no developer, and that WeDispatch needs no Kajabi-specific plugin to work.
The player fits in a custom code block
Kajabi lets you add custom code in two places: inside a page or post, through a dedicated code section, and across the whole site, in the theme header. That is the only mechanism we need. The player goes in with a single line:
``
<script src="https://wedispatch.fr/player.js"
data-article="ARTICLE_ID" defer></script>
Dropped into a code block within your article template, this line shows the player on every post that uses that template. You paste it once. It is exactly the principle behind our WordPress plugin, carried over to a platform that accepts no plugin: the player lives where you choose it to in the page, and nothing else in your Kajabi theme is changed.
Pointing the player at the right content
What remains is telling the player which audio belongs to which page. Two approaches, depending on how comfortable you are in Kajabi. The first lets detection work from the page address: you give us the URL, the text is read from the published page, the audio is matched. Nothing to create in Kajabi. The second, steadier one, gives the data-article attribute an identifier you keep even if the page address changes one day. Five minutes of setup, and a later URL redesign will not break anything.
Producing the audio: feed or API
Showing the player is not enough, you still have to make the file. If your Kajabi blog exposes a publication feed, you give us its address and new posts are picked up as they are published, with no action on your side. That is the route set out in full in feed-based auto-discovery, and it is the most comfortable for a team that wants to keep publishing as usual.
If you would rather keep control (choosing when generation happens, which voice, handling corrections), the call by API from your own publishing chain stays open. An automation tool such as Zapier or Make, fired when a Kajabi item is published, sends the text and retrieves the audio. It is a little more work up front, and it hands you the whole chain.
What the player leaves untouched
The code block adds the player and nothing else. It does not rewrite your pages, does not change your theme, does not create an account for your visitors, and depends on no internal Kajabi setting that could shift during a platform update. You can switch on read-along, where the text highlights as the audio plays, which helps dyslexic and low-vision readers, and synced subtitles are set from your WeDispatch dashboard, with no return trip into Kajabi.
When a piece of content changes
Correcting an article after publishing is common. If you go through the feed, the update is spotted and the audio flagged for regeneration: you relaunch once the text has settled, and successive corrections are never billed twice. If you go through the API, you send the same identifier with the corrected text. Either way, the audio already online keeps being served until you relaunch, so no page is left without a player in the meantime.
Where to start
For a Kajabi site, the quickest path is the code block in the article template paired with the feed when one exists: about fifteen minutes, no line of code to write yourself, and every new post ships with its audio version. If you want stable identifiers or precise timing, add the API. The simplest way to decide is to hear the player on your own texts before equipping the whole site, and to check what French actually sounds like along the way, which is the real question and the one we go into on the French text to speech page.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo