Skip to content
RRelinta
← Feature update

Use custom lead fields in outreach templates

Custom lead columns store text on the active workspace's lead records. They can supply variables to supported outreach templates. They are separate from custom company columns.

Create and edit a field

  1. Open Leads → Columns → Add custom column.
  2. Enter a clear name and create the column.
  3. Click a cell to enter its value.
  4. Click outside the editor or press Ctrl/Command+Enter to save. Enter adds a line; Escape cancels the edit.

If saving fails, use the displayed retry or reload action and check the value before moving on. Hiding a column changes the table layout; it does not delete its stored values.

Import values from CSV

Create the custom columns first. Open Import CSV and download the current template so you use the workspace's exact custom.<key> headers, together with the required profile identification fields.

Do not substitute the display name for the stored header or invent a new key. Unknown custom headers are rejected rather than creating a column automatically. Preview the file and resolve errors before starting the import. An empty CSV custom cell leaves an existing value unchanged; it is not a bulk-clear instruction.

Use a field in a message

  1. Open the relevant Playbooks message step and select Template mode.
  2. Type {{ and choose the custom field from the suggestions.
  3. Review the inserted token, such as {{custom.icebreaker}} for a field whose actual key is icebreaker.
  4. Preview messages against real leads, including one with a missing value.
  5. Fill required data and save the playbook before outreach.

Choose tokens from the catalog instead of guessing names. Do not assume a blank field has a useful automatic fallback. A generic message around a missing variable can lose its intended meaning.

Read about custom company columns if the information belongs to a company rather than a person.

Open Relinta · Read the feature update