Choose the right data source for campaign generation.

CSV

Best for batch generation, quick testing, and one-time lists.

Zapier

Best when a connected app event should trigger BHuman.

Pabbly

Best when a webhook builder sends object-style variables.

Leadr

Best for LinkedIn-style outreach workflows with optional video personalization.

API

Best when your product or backend controls generation and delivery.

CSV headers become campaign mapping options. Rows with all empty values are skipped during parsing, and large files are parsed in a worker path.

• Use one column per variable.
• Trim header names and keep them stable.
• Include URL columns for background mode assets when needed.
• Use a small test CSV before uploading a full list.

Zapier

Uses generated Zapier credentials from Settings and connects BHuman to supported Zapier apps.

Pabbly

Uses a simple payload where variables are supplied as object keys.

API generation uses either ordered rows or endpoint-specific payloads. For campaign generation, the variables array defines the order, and each nested array in names supplies one recipient row.

• Every required variable has a mapped source field.
• Mapped fields exist in the CSV headers or payload.
• Each row has a value for each mapped variable.
• Background mode columns exist before generation starts.
• Callback URLs and CTA URLs use HTTPS.