CRM variable mappings

CRM mappings give an external property a reusable Landit variable identity. They are configured for the connected user and provider; a matching field label in another account is not sufficient.

Configure a mapping

Connect the provider first, open its mappings screen, select the actual source property, and choose a clear Landit variable name. Save and reopen the mapping before using it in a template.

HubSpot exposes contact and company property selections. Outreach combines observed prospect attributes with custom property identifiers such as custom1 through custom150. Use the actual source key rather than a guessed friendly label.

Understand the reference

A mapping links a saved integration-variable identity to a provider’s source_key. The provider namespaces are hubspot and outreach. Copy the reference available in Landit and check the template manifest for the expected path.

Mapped aliases and raw CRM data are different. A source property may exist but be empty on a particular contact. Connecting a provider does not populate every field for every prospect.

Use mapped values in Pages

Generate Pages through the connected CRM workflow to use the mapped properties. An optional property can use a Liquid fallback when the source record has no value. Required inputs follow the template’s generation requirements.

When editing HubSpot mappings, submit the complete intended set: mappings omitted from the saved form are removed. Changing a mapping does not imply automatic regeneration of old Page data.