Merge Fields and Custom Variables in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Merge fields and custom variables are placeholders ({{like.this}}) that pull live data into Sparkforge messages and workflows. They cover standard fields, custom fields, custom values, custom objects, trigger links, and payment links.

Merge fields and custom variables are placeholders that Sparkforge replaces with live data when a message renders. They look like {{something.here}} and let you personalize emails, SMS, workflow steps, and templates without copy-pasting per contact.

Types of merge fields and custom variables

  • Standard Fields — built-in, non-customizable fields like contact names, appointment times, and user details.
  • Custom Fields — user-defined fields on contacts and opportunities.
  • Custom Values — reusable static values for templates and workflows.
  • Custom Objects — user-created data structures for advanced models.
  • Trigger Links — links that fire workflow or campaign actions when clicked.
  • Payment Links — links that let customers pay for products or services.

Company fields in contact workflows

When you build a contact-based workflow, the variable picker also lists Company fields. If the contact is associated with a Company record, steps and conditions can pull company name, phone, email, website, and address. If the contact has no associated company, those values resolve to blank.

Standard fields

Predefined fields available by default in every account. Examples:

  • Contact First Name
  • Contact Email
  • Appointment Date and Time
  • User Full Name
  • Company Name

Standard fields cannot be modified or deleted. You choose whether to use them.

Custom fields

User-defined fields per contact or opportunity. Common uses:

  • Customer preferences (preferred channel, etc.)
  • Membership tier (Gold, Silver, Platinum)
  • Product or service interest
  • Event registration / attendance
  • Account manager assignment
  • Contract renewal dates
  • Lead source (Facebook, Google Ads, referral)

Custom values

Reusable static placeholders for company-wide info. Common uses:

  • Company phone, email, and address in email footers
  • Standard sign-off phrases
  • Frequently used URLs (website, support page)
  • Legal disclaimers and compliance statements
  • Brand taglines
  • Reusable seasonal greetings

Updating a custom value updates every template and workflow that uses it.

Custom objects

Data structures that go beyond standard contact and opportunity fields. Useful for:

  • Subscription plans (plan type, renewal, billing cycle)
  • Inventory (SKU, quantity, supplier)
  • Property listings (location, price, features)
  • Vendor records (contacts, contracts, payment terms)
  • Detailed appointment metadata (service type, location, staff)

Trigger links

Links that fire actions when clicked. Common uses:

  • Webinar registration with auto-confirmation
  • Survey follow-up tagging
  • Resource downloads with engagement tracking
  • Upsell offer follow-ups
  • Event RSVPs and reminders
  • Limited-time offers with reminder triggers

Payment links

Links that collect payment for products or services. Common uses:

  • Event tickets
  • Recurring subscriptions or memberships
  • Physical and digital product sales
  • Booking deposits
  • Donations and fundraising

Default and fallback values

Sparkforge does not currently support fallback or default values for empty merge fields. An empty field renders as blank.

Workaround: conditional content

Use Conditional Send in the email builder to swap content based on whether a field has data:

  1. Block A: Hi {{contact.first_name}}, — sent when first_name is not empty.
  2. Block B: Hi Friend, — sent when first_name is empty.

The recipient sees one or the other, never both.

Syntax notes

  • Merge fields are case-sensitive. {{contact.name}} works. {{Contact.Name}} does not.
  • Test with a preview send or template preview to confirm the data resolves.

Frequently Asked Questions

What's the difference between custom fields and custom values?
Custom fields store unique data per contact or opportunity (like a birthday). Custom values are reusable placeholders for static info that's the same across the account (like your company phone number).
Why is my merge field blank or showing the literal placeholder?
Either the syntax is wrong (merge fields are case-sensitive) or the contact record has no value for that field. Verify the syntax — for example, {{contact.email}} — and confirm data exists on the record.
Are merge fields case-sensitive?
Yes. {{contact.first_name}} works. {{Contact.First_Name}} does not.
If I update a custom value, does it propagate everywhere?
Yes. Updating a custom value automatically updates every template and workflow that references it.
Can I bulk import custom fields or custom values?
Not currently. Custom fields and custom values must be created individually. There is no strict limit on how many you can create, but organizing them into folders keeps things manageable.

Was this article helpful?