Skip to main content

Data Fields

Paul Holder avatar
Written by Paul Holder
Updated over 3 weeks ago

Data Fields is a powerful feature that allows you to create your own fields in OnRamp and enter data into them.

What is a Data Field?

By default, OnRamp Objects (Playbook, Project, Task, User, Customer, etc.) have a number of fields associated with them.

For example, the Project Object has Name, Start Date, End Date, Owner, amongst others.

Data Fields allow you to create custom places to put data and information not provided by OnRamp out of the box.

Setting up a Data Field & How to Use Them

Let's say you wanted to track the revenue from a given customer.

You can add a custom Data Field to the Playbook Object to do so.

Note: Any Data Field added on a Playbook will also show on a Project that is created from that Playbook. Any value entered in the Playbook will also carry over to the Project (which can then be changed)

  1. Go to Settings > Data Fields > + Create Data Field

  2. Fill out the creation form. In this case we will creating this on the Playbook Object

    1. There are a number of field type options to choose from e.g., dropdown, text, date. In this case we will use a text type

  3. Click Save Field

The Data Field will be visible in various places depending on the Object you've chosen.

Note: Data Fields are not currently visible on the Customer Portal, meaning any that you choose to add will be visible to your team only

In our example, if I look at a Playbook > Data Fields tab, I can see the field we've created and enter in a value.

Data Fields in Webhooks & Reporting

Data fields are included in the payload of OnRamp triggers - meaning you can create Webhooks that leverage what you include in your Data Fields!

To check it out, go to Settings > Webhooks > Triggers to see the payloads.

Data Fields can also be used in Views and will also appear in data exports.

Select Example Use Cases

We're excited to see what else you come up with!

  • Project

    • Track support level, revenue, unique identifier, key milestone date, why they purchased, number of calls, link back to a usage dashboard

  • Task

    • Time spent doing, notify user of progress, note if it is a critical path task or not, link to a JIRA ticket or 3rd party system

  • Customer

    • Track customer type, address, segment, key contact information, unique identifier number, number of branches

Did this answer your question?