Pre-filled subtask answers
Updated
A pre-filled subtask answer is an answer OnRamp fills in for you. It comes from a field in your CRM or from an answer given in another task. You set it up on the subtask in the task builder, with its Data source setting.
When to use it
Use it when the information a task asks for is already known. For example, a task can show a deal's amount or close date from your CRM and ask the customer to confirm it. Or a later task can reuse a contact name collected earlier. People skip retyping, and they still get a chance to check the value is right.
How it works
Where you set it
The Data source dropdown appears only on inputs that can hold an answer: text, number, phone, text area, rich text, date, date-time, dropdown, radio and checkbox. It has three options:
Manually entered: the default. Someone types or picks the answer.
From another task: the answer comes from a field in a different task.
Linked to a CRM field: the answer comes from your CRM. This option appears only when a CRM is connected.
When you pick a source, the builder lists the fields from the CRM object or task you chose. Fields that can't fill this input are disabled, with a lock icon. Each field shows its type, so you can see why.
Linked to a CRM field
Choose a CRM object, then a CRM field. The CRM object picker lists any object on your connected CRM.
When a workflow creates the project, the answer is filled from the record that triggered it. That includes related objects the workflow brings in with the record. A blank CRM value is skipped, so the answer stays empty.
Then choose a Sync direction:
Fill once at project creation: the default. The answer is filled when the project is created, then left alone.
Keep reading from the CRM: a change in the CRM updates the answer. An answer given in OnRamp stays in OnRamp.
Keep writing to the CRM: an answer given in OnRamp writes to the CRM. A change in the CRM doesn't overwrite it.
Keep both in sync: changes go both ways. On a conflict, the more recent change wins.
Use Keep writing to the CRM or Keep both in sync when you want confirmed answers to go back to your CRM. Some directions show a lock icon and can't be chosen. The builder explains why in two cases: a direction you already saved is no longer allowed, or choosing another field sets the answer back to filling once. For example, the CRM computes the field, the CRM marks it read-only, or writing back would change the value the CRM holds.
From another task
Choose a Task, then a Field on that task. When someone completes the source task, its answer fills the subtask. That person can be someone on your team or a customer in the customer portal.
Task status
When at least one answer in a task is filled this way, the task moves from Not Started to In Progress. A task that has already started keeps its status.
Limits
Structured CRM fields, such as compound address or location fields, can't be used.
A radio or dropdown stays empty if the CRM value doesn't match one of its choices.
From another task doesn't offer fields in the same task, or fields inside repeating lists or tables.
An answer from another task isn't filled if the destination task is already finished or the field already has an answer.
If the source field is deleted or changes type, the builder shows:
The previously selected source is no longer available.Choose another task and field.If your CRM can't be reached, the source shows as Linked to a CRM field (unavailable) with a warning. The link stays as it was until the CRM is available again.