Skip to main content

Use Merge Fields to Personalize Projects Automatically

Instead of manually editing every new project, you set it once and let automation do the heavy lifting. Less typing, more onboarding magic. ✨

Dylan Main avatar
Written by Dylan Main
Updated over a month ago

Merge Fields let you automatically personalize projects created from Playbooks by pulling in dynamic data—like customer names, product details, or account manager info—from OnRamp or your CRM. Instead of manually editing every new project, you set it once and let automation do the heavy lifting. Less typing, more onboarding magic. ✨


What Are Merge Fields?

Merge Fields are placeholders you add to Playbooks that automatically populate with real data when a project is created. They help you tailor project names, messages, tasks, and more—instantly and consistently.

You can use Merge Fields across:

  • Projects

  • Modules

  • Tasks

  • Subtasks

Example
[Customer Account Name] | [Customer Contact Name] | [Onboarding Product Name] | [Customer ID]

Kryptonite Inc | Clark Kent | Cape Cleaning | CC-22344

This means every project feels custom-built, even though it’s fully automated. 🧠💡


Where You Can Use Merge Fields

Merge Fields can be added almost anywhere text appears in a Playbook, including:

Project-Level Fields

  • Project Name (internal & customer-facing)

  • Project Description (internal only)

  • Project Welcome Message (internal & customer-facing)

Common uses

  • Customer account or contact name

  • Product being onboarded

  • Account manager name and contact info

  • Links to CRM records or booking calendars


Module, Task, and Subtask Fields

  • Module Name

  • Task Name

  • Task Description

  • Subtask Name

  • Subtask Description

  • Text instruction subtasks

  • Paragraph form elements

Examples

  • Introduction to [Product Name]

  • Meet Your Implementation Specialist: [Account Manager Name]

  • A task description that includes phone, email, or a scheduling link—all auto-filled.


When Should You Use Merge Fields?

Use Merge Fields when you want onboarding projects to:

  • Feel personalized from the moment they’re created

  • Pull in data like account names, owners, or links automatically

  • Start immediately—no post-creation cleanup required

If you’re scaling onboarding, this is your secret weapon. 🚀


Merge Fields vs. Data Fields vs. Task Fields

These tools work together, but they serve different purposes:

Merge Fields

  • Display dynamic information to admins and customers

  • Can pull data from external systems (like Salesforce)

  • Used for personalization across projects, tasks, and messages

Data Fields

  • Store and display information inside OnRamp

  • Can be filled manually or via automation

  • Live on projects and can appear in the portal

Task Fields / Forms

  • Control how customers complete tasks

  • Collect responses (text, dropdowns, uploads, etc.)

  • Can include Data Fields, but not Merge Fields directly

Think of it this way:
Merge Fields show info. Data Fields store info. Task Fields collect info. 🧩


Set Up Merge Fields

Step 1: Add Merge Fields to a Playbook

Use Merge Fields anywhere you want content automatically populated when a project is created.

  1. Go to Library → Playbooks

  2. Open a Playbook

  3. Click the Merge Fields tab

  4. In supported text areas, type /merge and select the field you want

Supported areas include:

  • Project Name

  • Project Description

  • Project Welcome Message

  • Module Name

  • Task Name & Description

  • Subtask Name & Description

  • Text instruction subtasks

  • Paragraph form elements


Step 2: Map Merge Fields in a Workflow

Merge Fields come to life when mapped in a Workflow.

  1. Go to Workflows

  2. Choose a trigger

    • Example: Salesforce → Opportunity = Closed Won

  3. Add an action to Create Project from Playbook

  4. Map values for:

    • Project Name

    • Project Data Fields

    • Project Merge Fields

  5. Save and Publish the workflow

That’s it. From here on out, projects create themselves—fully personalized and ready to roll. 🎉


Tips & Troubleshooting

  • If a Merge Field shows as blank, double-check that the workflow is mapping a value to it.

  • Keep Merge Field naming consistent to make Playbooks easier to maintain.

  • Test workflows with a sample record before going live—future you will be grateful.

Did this answer your question?