← All articles

Personalized Video Workflow Checklist: Plan Your Data, Video, and Campaign

By BHuman Editorial TeamPublished

Use this practical checklist to choose a recipient-data source, prepare a video template, test personalization, and decide where personalized videos belong in your campaign.

On this page6 sections

Start with the campaign decision

Before choosing a data source, decide who should receive a personalized video, what each video should say, and where it fits in your campaign. A useful workflow connects a ready video template to recipient data, then generates a video for each row or request.

Write down the audience, the personalized details, and the next action you want a recipient to take. Keep the first test small: confirm the message and data mapping before preparing a full list.

  • Audience and campaign purpose are clear.
  • Personalized details are limited to values you can supply for each recipient.
  • The video has a defined place in the campaign, such as a sales outreach or marketing sequence.
  • A small test can check the template and recipient data before a larger run.

Choose how recipient data will arrive

For a manual batch, one-off list, or quick test, CSV or Excel is the straightforward choice. Use Zapier when a connected-app event should trigger generation, Leadr for LinkedIn-style outreach workflows, Pabbly for object-style webhook payloads, or the API when your product or backend needs to control generation.

BHuman campaign setup uses a ready AI Studio template and recipient data. The current setup interface exposes CSV/Excel, Zapier, and Leadr; Pabbly and API are integration paths. Choose the least complex source that matches how your campaign will run.

  • CSV or Excel: batch lists, one-time campaigns, and test rows.
  • Zapier: generation triggered by a connected app event.
  • Leadr: LinkedIn-style outreach workflows.
  • Pabbly: object-style webhook payloads.
  • API: product- or backend-controlled generation.

Prepare the video and its variables

Start with a ready template that has a source video and at least one variable. Each variable marks a detail that recipient data will supply, such as a first name. Keep fixed words in the template and send only the replacement value in your data.

For example, if the template says “Hi, [first_name],” the data value should be “Alex,” not “Hi, Alex.” This keeps the personalized field separate from the words already recorded in the template.

  • A source video exists on the template.
  • Every variable has a clear meaning and a corresponding data field.
  • Variable names and data headers are stable and easy to map.
  • Each recipient row has a value for every required variable.

Map and test the recipient data

For CSV or Excel, use one column per variable, trim header names, and keep them consistent. Upload the file and preview its rows before mapping columns to template variables. A small test file can reveal missing values or mismatched headers before you use a full list.

For an API campaign, variables define the field order and each names row supplies values in that same order. The API workflow requires an existing campaign and template; it does not create a presenter video from a prompt. API access is in beta, and production REST credential provisioning is on hold pending qualification, so confirm eligibility before planning a production integration.

  • Every required variable maps to a CSV header or payload field.
  • Each row contains a value for each mapped variable.
  • Values contain replacement text only, not fixed template wording.
  • For API data, each recipient row matches the ordered variables.
  • If using API, account for beta access and the production qualification restriction.

Choose the generation approach and extras

If you use BHuman campaigns, choose Mini or Max for the viewing mode. Mini places the presenter over backgrounds, so personalized moments need background coverage; generic backgrounds can be added for missing coverage. Max produces full-screen HD and can be limited by plan or face-distance checks.

Add extras only when the campaign needs them. Campaign setup includes options such as subtitles, manual audio, background mode, landing page URLs, and callbacks. Background-mode rows need valid URLs or uploads for each timed segment. Check the campaign’s validation requirements before generating.

  • Decide whether Mini or Max fits the planned video presentation.
  • For Mini, check background coverage for every personalized moment.
  • If using timed background segments, provide valid media for each segment.
  • Use subtitles, manual audio, or other extras only when they serve the campaign.

Run the checklist before launch

Campaign generation is asynchronous: a submitted campaign may be queued or processing before videos are ready. Use the generated videos page to monitor outcomes, including succeeded, failed, and needs-review results. Check the account’s generation availability and quota as part of preflight.

For API submissions, save the returned generation IDs and check each result before using its video. Do not blindly repeat a paid POST after a timeout: the API guide says repeated submissions can create additional work and charges, and there is no documented idempotency key.

  • A source video and valid data source are attached to the campaign.
  • All required variables map to fields that exist and contain values.
  • Background and manual-audio requirements are met, if applicable.
  • Generation is available and the account has enough quota.
  • You have a plan to monitor results and handle failures before sending videos to recipients.