Skip to main content

Create and Use Data Fields in OnRamp

Use Data Fields anytime you need to track information unique to your business process.

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

Summary / When to Use This

Data Fields let you store custom information across OnRamp—whether at the account, project, playbook, or task level. They help you capture important details (like region, renewal date, or implementation manager) and use them in automations, workflows, and reporting. Use Data Fields anytime you need to track information unique to your business process.


Steps to Follow

1. Navigate to Data Fields

  • Go to Settings > Data Fields.

  • Click + Create Data Field in the upper right.


2. Define your field details
Fill out the form:

  • Name: Give it a clear label (e.g., “Internal Onboarding Status”).

  • Description: Add context so teammates know how to use it.

  • Object type: Choose where the field belongs (Account, Internal User, Customer User, Playbook, Project, or Task).

  • Field type: Choose the kind of data to collect:

    • Dropdown

    • Text

    • User

    • Date

    • Number

    • Currency

    • Color

    • Link


3. Configure options

  • Default Value (optional): Pre-populates the field until it’s changed.

  • Required Value: Toggle On if this field must be filled in.

  • Add on creation: Toggle On to automatically include this Data Field whenever a new record of that type is created.


4. Save your field
Click Save Field in the top right. The new Data Field will now appear in your Data Fields list.


5. Use Data Fields on objects

  • Open a Project, Playbook, or Task and go to the Data Fields tab.

  • Add values for the Data Fields you created.

  • These values can then power automations, be shown in customer portals, or support reporting.


Tips & Troubleshooting

  • Not sure where to create the field? Use the Account object type if you want the field tied to the customer across multiple projects.

  • Want consistency? Add fields at the Playbook level so they’re included every time you launch a new project.

  • Archiving: Old or unused fields can be archived instead of deleted, so you don’t lose historical data.

  • Integrations: Align Data Fields with CRM fields (like Salesforce or HubSpot) to keep systems in sync.

Did this answer your question?