Troubleshooting Blank or Broken Merge Fields

Last updated: February 18, 2026

If you’re seeing:

  • {{company_name}} instead of a real value

  • A blank space where a value should appear

  • The wrong value showing in a task

Don’t panic.

Merge fields are deterministic — if something looks wrong, it’s almost always because the underlying data wasn’t populated or mapped correctly.

This guide walks you through exactly how to diagnose it.

First: Understand What a Merge Field Depends On

A merge field does not generate data.

It simply pulls from one of these sources:

  • A Playbook Data Field

  • A CRM-mapped value

  • A Project-level system value (like Project Owner)

  • A User-level value (like a booking link)

If the source is empty or missing, the merge field will render blank — or not resolve at all.

Scenario 1: The Merge Field Shows as {{field_name}}

If the raw syntax appears instead of resolving, this usually means:

  • The field was typed manually and misspelled

  • The merge field no longer exists

  • The field name changed

  • The content was copied from outside the editor

Fix

  1. Delete the merge field

  2. Type / in the editor

  3. Re-select the correct field from the list

  4. Save and re-test

Always insert merge fields using / — never manually type the syntax.

Scenario 2: The Field Renders Blank

If the merge field resolves — but shows no value — the source data is likely empty.

Ask:

  • Was the Data Field mapped in the Workflow?

  • Does the CRM record actually contain a value?

  • Is the integration user able to read that field?

  • Was the field populated before project creation?

Remember:
Merge fields don’t backfill automatically unless the underlying value exists.

Scenario 3: CRM-Mapped Value Didn’t Populate

If your merge field references a Data Field populated during Workflow execution:

Check the Workflow version:

  1. Go to Workflows

  2. Open the relevant Workflow

  3. Confirm you’re on the active version

  4. Review the Project Data Fields card

  5. Ensure the correct CRM field is mapped

If the Workflow ran before the mapping existed, older projects will not update retroactively.

Scenario 4: Project Owner Fields Are Blank

If you’re using system-level values like:

  • {{project_owner_name}}

  • {{booking_link}}

Check:

  • Does the assigned user have the required value set on their profile?

  • Was ownership changed after project creation?

If the source user profile is missing the value, the merge field will be blank.

Scenario 5: The Value Is Wrong

If the merge field resolves — but shows the wrong value:

Check:

  • Did the Workflow map the correct CRM field?

  • Are there multiple Workflows creating projects?

  • Did the Playbook change after projects were created?

  • Was the CRM record updated after project creation?

Merge fields reflect stored project data — not live CRM lookups unless designed that way.

Important: Merge Fields Don’t Update Automatically

In most cases, merge fields resolve:

  • At project creation

If a project was created before:

  • A Data Field was added

  • A Workflow mapping was corrected

  • A user profile value was populated

The project will not automatically re-render historical values.

You may need to:

  • Update the underlying field

  • Or recreate the project for testing

A Simple Debugging Flow

When a merge field looks wrong:

  1. Identify which field it references

  2. Identify where that data is supposed to come from

  3. Confirm the data exists

  4. Confirm the Workflow mapped it

  5. Confirm the correct Workflow version was active

  6. Re-test with a new project

Most merge field issues are upstream configuration issues — not merge field issues.

Best Practices to Avoid Broken Merge Fields

  • Always insert fields using /

  • Keep Data Field names clean and consistent

  • Avoid renaming fields after publishing Playbooks

  • Test with real CRM records

  • Ensure required CRM fields are populated before trigger stages

Structure first. Personalization second.

When to Contact Support

Reach out if:

  • Merge fields resolve inconsistently

  • Values populate intermittently

  • Data appears correct but doesn’t render

  • System-level fields behave unexpectedly

Bring:

  • Project name

  • Workflow name

  • Merge field used

  • Screenshot of the rendered result

  • Screenshot of the underlying Data Field value

That makes diagnosis fast.