Merge Fields and Custom Variables in Kyrios

A merge field is a dynamic placeholder that pulls saved data into a message or template. A merge field usually looks like this:

{{contact.first_name}}

When the message is sent, Kyrios replaces the merge field with the saved value from the matching record. Example:

Hi {{contact.first_name}}! This is {{user.name}} from {{location.name}}.

Merge fields can be used in areas where Kyrios supports dynamic personalization.

Common places include:

If a merge field has no saved value, Kyrios replaces it with a blank space. Kyrios does not currently support default or fallback values for empty merge fields.

Example: Hi {{contact.first_name}},

If the contact has no first name saved, the first name area appears blank.

Use Conditional Sending in the email builder when you need different content to show based on whether a field has data. Example setup:

Standard fields are built-in fields available by default in Kyrios. Standard fields cannot be modified or deleted. Common standard fields include:

Contact-based workflows can use company fields in the variable picker. Company values only populate when the contact is associated with a company record. If the contact is not associated with a company record, the company merge field resolves as blank.

Custom fields are user-defined fields that store unique data for contacts, opportunities, or supported objects. Use custom fields when the value changes from record to record. Examples include:

Workflow merge fields can include built-in system fields in addition to saved custom values. Examples include:

Some fields only appear when the workflow has the correct context. For example, Task ID appears in task-related workflows.

Custom values are reusable placeholders for information that should stay consistent across multiple assets. Use custom values when the value is the same in many places and may need to be updated later. Examples include:

Custom objects are user-created data structures for storing advanced business information beyond standard contact fields. Use custom objects when you need to manage a separate type of record with its own fields. Examples include:

Trigger links are special links used inside emails or SMS messages. When a contact clicks a trigger link, Kyrios can track the click and trigger workflow actions. Common uses include:

Payment links allow customers to pay for a product, service, deposit, donation, ticket, or subscription from a shareable link. Use payment links when you need a fast way to collect payment without building a full checkout page.

The matching record may not have a saved value for that field. Add the missing value to the contact, company, user, or related record.

Check the merge field syntax. Merge fields must use the correct format, such as {{contact.email}}.

Company fields only populate when the contact is associated with a company record.

Kyrios does not currently support fallback values for empty merge fields. Use Conditional Sending in the email builder as a workaround.

Custom fields store unique data for individual records. Custom values store reusable information that can be used across multiple templates, workflows, websites, and funnels.

Yes. Merge fields are case-sensitive. For example, {{contact.name}} and {{Contact.Name}} are not the same.

Kyrios replaces the merge field with a blank value.

No. Standard fields are built in and cannot be edited or deleted.

Yes. Custom values can be used to display consistent, reusable information across websites and funnels.

Yes. Custom values can be organized into folders.

No. Custom fields and custom values must be created individually.

Yes. A trigger link can trigger workflow actions when a contact clicks the link.