CSV import and mappings

Use a CSV when you want to review a prospect list and map template inputs before generation. Start with one row to check both the file and the selected template.

Prepare the file

Use UTF-8, comma-separated values, and a lowercase .csv extension. Headers are case-sensitive. Include the exact linkedin_url column and one person per row.

linkedin_url,offer
https://www.linkedin.com/in/example-prospect/,A tailored product walkthrough

Replace the example profile with your intended test prospect. Quote values containing commas, quotes, or line breaks according to CSV rules. A spreadsheet export is preferable to manually assembling complex rows.

Match template inputs

Select the intended template and map its unprefixed input variables to source columns. Do not put a saved user value, prompt definition, or asset reference into a CSV merely because it appears in the manifest; those have their own context sources.

Check that every required input has a usable value on every intended row. If your template has no unprefixed inputs and the mapping screen prevents continuing, contact Landit with the template slug and reported error.

Review the output

The results CSV contains url and error, plus enrichment columns including justlandit_job_title, justlandit_company, justlandit_years_at_company_in_month, and justlandit_picture_url.

Keep the original file and compare rows. A batch containing an error does not mean all rows failed. Correct only the affected rows before resubmitting, and retain successful URLs to avoid duplicates. Read Create your first Page for the full walkthrough.