Variables and input requirements

A template’s manifest distinguishes supplied input variables from system-backed variable paths. Read it before choosing a creation method or preparing a prospect list.

Match the variable to its source

Reference	Where its value comes from
`offer`	A per-prospect input supplied for the template.
`linkedin.first_name`	Prospect profile context.
`user.booking_link`	The Page owner’s saved user variable.
`prompt.opening`	A saved prompt definition and its generated result.
`user_asset.product_image`	An accessible uploaded image.
`hubspot.segment`	CRM context, including configured mappings.

These are examples, not identifiers automatically created in your account. Copy actual saved identifiers and the selected template’s manifest.

Supply inputs correctly

For CSV, provide columns and map the required unprefixed inputs. For MCP, put each input directly on its prospect object. Do not assume an input supplied in one batch becomes an account-wide default.

For shared templates, check that the Page owner has the required prompt and user definitions. Sharing the template does not copy another person’s private definitions.

Check missing values

Optional rendering values can be blank or use a Liquid fallback. Required generation dependencies can fail a PageRun instead of rendering blank. Read Understand variables for the full ownership and missing-value rules, and test one prospect before submitting a larger list.