Create Branded Text Videos with Claude and Prolifik

Connect the account that owns the brand

Use the current Prolifik MCP connection guide with Claude's remote connector instructions. Account and workspace controls determine which connections and actions you can use. Authenticate through the connection flow rather than putting passwords or access tokens into a message.

Start with a read request: “List my Prolifik brands, then show the voice and audience for the brand I choose.” This prevents a remembered name from quietly selecting the wrong workspace brand. Ask Claude to keep the returned brand identifier for the creation request.

Prolifik's Claude connection supports the content and clipping workflows covered here. AI Studio and cloning tools are not available through that Claude connection. This article uses the existing Text Story format, so those separate capabilities are unnecessary.

Give the video one recognizable situation

Our fictional brand, Pantry Window, helps people plan dinners around food already at home. The intended viewer opens the fridge after work and still cannot choose a meal. The video should offer one useful action: pick the ingredient that needs using first.

Give Claude the premise and the limits together:

We are making one Pantry Window Text Story for people deciding what to cook tonight. The useful action is choosing the ingredient that needs using first. Write short on-screen copy in a calm, practical voice. Do not invent nutrition claims, recipes or customer results. Show me the copy before rendering.

The instruction supplies a creative problem Claude can solve. It does not ask the assistant to manufacture proof about the product. If the idea comes from a specific page, provide the page or a verified source already stored in Prolifik and check what the assistant extracted.

Turn the idea into exact on-screen copy

A possible fictional script is:

Open the fridge before you open another recipe. Find the ingredient that needs using first. Build tonight's dinner around that. Tomorrow's plan can wait.

Each sentence advances the thought. The first establishes the situation; the middle gives the action; the final line limits the task. Asking for five additional benefits would make this small idea harder to read.

The Text Story format presents text over video. It does not demonstrate that the fictional app has scanned a refrigerator or selected a meal. Choose background material that supports the everyday setting without pretending to show a product action.

Ask Claude to preserve the agreed wording: “Use that exact copy for one piece, not a new variation.” In the current tool schema, non-carousel content uses a text value inside customTexts. Carousel content uses slides instead. Mixing those shapes is a request error, not a writing problem.

Submit one rendered draft

For this example, Claude should construct a create_content_job request with the selected brandId, the kinetic-type format, a count of one and deliveryMode set to download. The approved script belongs in one customTexts entry. An idempotency key identifies the particular creation attempt.

You can express the same instruction without writing JSON:

Create one Prolifik Text Story using the selected brand and the exact copy above. Use download delivery. Include our saved logo if it is configured. Choose calm supporting footage and no music. Keep the job ID and return the finished video when rendering completes. Do not publish it.

The assistant should check the available usage before making a request that consumes renders. It should also use the tool's actual filters rather than invent an arbitrary style field. In this format, assetFilters.audioMood can be none for silence.

Retrieve the job you already created

Creation is asynchronous. The first response identifies work in progress; Claude should keep that identifier and use get_content_job to retrieve its status and pieces. If the response is lost, recover the existing request rather than treating the lack of an answer as proof that nothing happened.

When the job reaches a review state, ask for the piece identifier, script and rendered media. A failure should remain visible. The assistant should not replace an unsuccessful render with a confident sentence saying the video is ready.

Signed media links expire. Keep the piece identifier with the project notes so a current link can be retrieved later. That is more useful than preserving only a temporary download address in a chat bookmark.

Review the words as moving content

Play the complete file at a phone-sized width. Read it without pausing. The copy may be excellent on a page and still feel crowded when displayed over moving footage. Inspect line breaks, the opening frame, logo placement and the last readable moment.

If “ingredient that needs using first” wraps poorly, shorten the wording deliberately rather than asking for a wholly new video. update_content_piece supports copy changes and queues another render. Retrieve that replacement and review it too; changing the text starts a new rendering step.

The caption readability guide covers practical text checks that also help with a Text Story. Once the file works, download it or make a separate request for a specific connected publishing destination. The result of this workflow is one inspected video with a known source message, not an unexamined batch of variations.