Dynamically Populating Data in Project Answers

Last updated: July 28, 2026

Instead of leaving every task answer to be filled in by hand, you can set a subtask to pull its answer automatically from another source. On any subtask, choose the data source that populates it: Manually Entered (the default, and how everything works today), From the CRM, or From Another Task. In every case, OnRamp only shows fields that are compatible with the subtask’s field type — you can’t map a radio button into a free-text field, for example.

From CRM at Creation

When a subtask’s data source is set to the CRM, you choose a CRM object to pull values from. Today, that object has to be the triggering object of the workflow — in other words, whatever record (for example, an Opportunity) kicked off the project.

  • Select the fields you want to pre-populate from that object — name, description, amount, dates, numbers, radio buttons, and pre-populated select fields are all supported.

  • Once the workflow runs off that CRM trigger, OnRamp fills in the task answers automatically, and those tasks show as In Progress because they’re already filled out.

  • You can confirm this in the project itself: open a task’s Details tab to see the subtask responses populated directly from the CRM. The same holds true in the customer portal for customer-facing tasks.

From Previous Task Answers

You can also pull a subtask’s answer from a task completed earlier in the same playbook by setting its data source to From Another Task.

  • Pick any other task in the playbook, then choose which field on that task to map in.

  • As with CRM mapping, only compatible fields are shown as options.

  • Once the source task is saved and completed — whether by an internal user or a customer in the portal — the mapped value flows into the destination subtask automatically, and that task moves to In Progress.

  • This works across field types, including text, numbers, and dates.

Where This Is Configured

Both data sources are set at the subtask level inside the playbook builder, as part of defining how each task’s answers get filled in.

Common Questions

What are use cases for this?

A common use case is confirming data from a CRM or a previous task inside a task itself. This lets teams skip manual entry for information that’s already known, while still giving the user a chance to validate that the information is correct. Once confirmed, any changes can be written back to your CRM via automations.

Why did my data not populate?

  • Today, only fields on the triggering object of the workflow will populate from the CRM. Populating data from a related record is coming soon — we’ll update this article once it’s available.

  • Confirm the data is available on the source record. For example, if you’re trying to populate a radio select or dropdown but the CRM value isn’t one of the available choices, the field will stay empty.