How to Match Personalized Video Fields to Your Sales Process

Start with the sales moment, not the spreadsheet

Match personalized video fields to your sales process by deciding what each video should help a sales rep do, then mapping only the recipient details that the video actually uses. BHuman campaigns connect a video template to recipient data: each row supplies variable values for one generated video.

Keep the mapping focused. A prospect’s first name may fit a personalized greeting; other details belong only if your template has variables for them. Recipient fields do not automatically create new video content or sales actions.

Build a simple field-mapping worksheet

Use this worksheet before preparing a CSV or API data. Start with the video template’s variables, then identify the matching source field and check what each recipient row must contain.

• Sales step: What conversation or outreach moment is this video for?
• Template variable: Write the variable name used in the video template.
• Recipient source field: Name the CSV column or API payload field that supplies it.
• Value rule: Record the exact replacement text expected, without fixed words already in the template.
• Validation: Check that the field exists and each recipient has a value.

Map fields for CSV or Excel batches

For a manual batch, use CSV or Excel. BHuman uses spreadsheet headers as mapping options and previews rows so you can map variables before generation. Use one column per variable, keep header names stable, and try a small test file before uploading a full list.

For example, imagine a template variable named first_name and a CSV column with that header. Put “Alex” in the recipient’s row—not “Hi Alex” if “Hi” is already part of the template. Send only the text that replaces the variable.

• Use the same headers across rows and include a value for every mapped variable.
• Keep variable values limited to replacement text; don’t repeat fixed template wording.
• If the campaign uses background mode, include the required background asset columns before generation.

Map API fields in the same order as the template

For an API campaign, BHuman uses an ordered variables array and a names matrix: each nested array in names represents one recipient row, and its values must match the variables in order. For example, variables ["first_name"] pairs with a recipient row ["Alex"].

The REST API personalizes an existing AI Studio template or campaign; it does not create a Speakeasy presenter video from a prompt. API access is beta, and production REST credential provisioning is on hold pending qualification. Confirm your use case with support before production use.

• Map each required template variable to a payload field or ordered value.
• Send replacement values only, not the surrounding fixed words from the script.
• For structured requests, set generation_mode explicitly to keep_original or full_script.

Choose a data source that fits the workflow

Choose based on how recipient data reaches the campaign. CSV or Excel fits batch generation, quick tests, and one-time lists. The available documentation also describes Zapier for connected-app triggers, Leadr for outreach workflows, Pabbly for object-style webhook payloads, and the API when your product or backend controls generation and delivery.

These sources serve different workflow needs; they do not make every sales system or action automatic. For API use, account eligibility, credits, and beta restrictions still apply.

• Use CSV or Excel when you want to prepare and review a batch manually.
• Consider a documented automation source when a connected app or workflow builder should trigger generation.
• Use the API only when your product or backend needs direct control and your use case is qualified.

Run the mapping checks before generating

Before generating videos, verify that the source is attached, every required variable is mapped, mapped fields exist, and every row has a value for each mapped variable. For campaigns using background mode, confirm the required background coverage too.

Generation is asynchronous. After submission, use the generated videos view to monitor statuses such as queued, processing, succeeded, failed, or needs review. A request being accepted does not mean a video is ready to play.

• Check field names and value order against the template variables.
• Review a small test row before preparing a larger list.
• For API requests, review the campaign’s credit estimate and account balance before sending.