Turning help docs into short how to videos
Help center articles already contain a script. "Go to Settings, click Billing, choose Update card" is a list of steps, and that is exactly what a product recording takes as input. This is the workflow I would set up for a support team that wants a short video on its most visited articles.
Map the article to steps
Take an article like "How to invite a teammate" and write its steps as a recording. Use a test account on your real app.
POST /v1/recordings
{
"url": "https://app.example.com/settings/team",
"viewport": "desktop",
"steps": [
{ "type": "hold", "seconds": 2, "mark": "team page" },
{ "type": "click", "selector": "text=Invite" },
{ "type": "type", "selector": "input[name=email]", "text": "sam@example.com" },
{ "type": "click", "selector": "text=Send invite" },
{ "type": "wait_for", "selector": ".invite-sent" },
{ "type": "hold", "seconds": 3, "mark": "sent" }
]
}The recording types at human speed and shows the cursor, so a viewer can follow along. Recordings can run up to 60 steps and 300 seconds. Each one is 3 credits.
Add narration and captions
For a silent loop embedded in the article, the recording on its own may be enough. For a narrated version, write a short script that uses the recording as its main scene, then render it.
A script is 2 credits and a render under a minute is 12, so a narrated how to video costs 17 credits including the recording.
Keep them current
This is the part I care about most. When the UI changes, a screenshot based tutorial quietly goes stale. Here you update a selector or a step and record again for 3 credits, then render the same script again. An agent can run that whenever a release touches the page.
Accessibility
Captions are timed to each spoken word, which helps viewers who watch with sound off and makes the video usable without audio.
See product recordings or get started.