Can You Import CSV Custom Variables into Unify Sequences?
Yes. You can import CSV values into Unify, map the columns to person or company attributes, and use those attributes as variables in sequence templates. The complete path is CSV column → mapped record attribute → selected template variable. Uploading a column does not automatically establish that it has become a usable custom variable.
The import documentation describes mapping CSV columns to Unify fields. The template-variable documentation confirms that templates can use custom attributes on people, companies, and related records. Before enrollment, verify the destination object, the saved value, and the rendered email.
Choose the destination attribute before importing
Decide whether each value describes the person or the company. That choice determines where it is stored and which object you select when inserting the variable. A value describing one recipient should not be mapped to a company attribute merely because that field has a similar name.
If the destination does not exist, follow Create attributes: open Settings → Data management, select the object, and choose Create attribute in its Attributes tab. Select the Attribute type and enter an Attribute name. Review the generated Attribute API name and any requirements or allowed options before saving.
The documentation states that the type, API name, Required setting, and Unique setting are fixed after creation. Choose them deliberately. An attribute’s existence does not prove that every CSV value is compatible with it; review the mapping and import warnings rather than promising arbitrary field-type support.
Use this blank mapping worksheet to agree on the destination before uploading. It is a planning aid, not a completed import or a record of tested results.
| CSV column | Destination object and attribute | Type and requirements |
|---|---|---|
| [Column header] | [Person or company] → [attribute name] | [Type]; [required?]; [allowed options or uniqueness?] |
| [Column header] | [Person or company] → [attribute name] | [Type]; [required?]; [allowed options or uniqueness?] |
Map the CSV and inspect the saved records
Prepare a CSV with a header row and a file size within the documented 20 MB limit. Include the identifying fields for the list type and any required custom fields. The bulk CSV enrichment workflow covers broader input preparation and enrichment checks; this article focuses on using the resulting values in copy.
- Open Leads → Lists, click New list, and choose Upload CSV. For an existing list, use Add records → Upload CSV.
- Choose companies or people, upload the file, and click Next to review mappings.
- Adjust suggested matches and map the custom columns you intend to use. People uploads have separate person and company mappings.
- Review the preview, required-field warnings, invalid values, and any enrichment choices. Click Start upload when the configuration is correct.
- Open the destination list, then Activity and the CSV upload to review the completed operation. Inspect the intended attributes on the resulting records.
Unify matches companies by domain and people by email. Mapped uploads can update existing records, so review values before starting. Rows can be skipped when identifiers or required values are missing or invalid; requesting enrichment does not guarantee a match. Use the list-building workflow to inspect the actual membership rather than treating an accepted file as proof that every row is usable.
For contact-oriented files, the target-account contact workflow helps distinguish finding the correct person from populating personalization fields. Both matter: a populated custom attribute on the wrong contact is not a successful personalization setup.
Select the custom attribute in the sequence template
Open the relevant email step in your sequence. Type { or click the variable icon, choose the appropriate object, and browse or search its attributes. Select the intended custom attribute from the selector. Use the actual field, rather than assuming a CSV header typed as plain text will resolve into a variable.
Related-record variables can follow up to three references, and each reference must point to a single record. Check the whole path when using company or other related data. An empty relationship can prevent resolution even when a similarly named value exists elsewhere.
The sequence creation guide explains authoring the sequence itself. Importing custom data solves how recipient values reach personalization; it does not require the message to be AI-written. For the separate authoring question, see creating a Unify sequence manually without chat. The sequencing product overview and personalization options provide context for choosing the appropriate content method.
Handle missing values with a complete fallback
Unify documents that emails with missing required variables are blocked from sending. A missing attribute or an empty reference in the path leaves the variable without a value. Fill the correct record field or use a snippet fallback; do not assume the system silently removes the missing phrase.
In Snippets, open Snippets → New snippet → Snippets. Write the reusable text under Content, using { to insert the variable. Under Fallback, write the complete alternate passage. The fallback replaces the entire snippet, not only the missing variable, so it must fit the surrounding email.
Insert the snippet into an email step with ; or the scissors icon. Expand the preview with the arrow beside the editor, choose a person under To, and turn on Fallback to check the alternate version. If you want a generated passage instead, smart snippets use prompts and recipient variables; that is a separate choice from storing imported values.
Check the full path before enrollment
Use permitted sample records to review a populated field, a missing field, and any required related-record path. These are proposed checks, not a claim that an import was performed for this article. Confirm the saved attribute, selected variable, rendered copy, and fallback behavior before authorizing outreach.
Keep imported research truthful when it becomes message text. The research-to-outreach workflow helps connect a verified finding to a relevant message. If the finding is unavailable, a fallback should remain accurate rather than inventing an observation.
Finally, inspect enrollment status for blocked content or missing-variable warnings. Correct the underlying value or template and verify the result. A successful upload and a send-ready email are separate outcomes; checking both is what completes the CSV-to-sequence workflow.
Frequently asked questions
Can a CSV column become a custom variable in a Unify sequence?
Yes, by mapping the column to the intended person or company attribute and selecting that attribute as a template variable. Uploading an arbitrary column alone does not establish that path.
Do I need to create the custom attribute first?
Confirm that the intended destination exists. If it does not, create it on the appropriate object with the correct type and requirements before mapping the CSV values.
How do I insert the imported attribute into an email?
Type { or click the variable icon in the editor, choose the appropriate object, and select the attribute. Confirm the value on the recipient’s record and in the email preview.
What happens when a required variable has no value?
The documentation states that emails with missing required variables are blocked from sending. Fill the data or use an appropriate snippet fallback.
Does a snippet fallback replace only the missing variable?
No. It replaces the whole snippet. Write a complete alternate passage and use the Fallback preview to check it in the surrounding email.
