Subtask Types

Every subtask you build in OnRamp's task builder falls into one of two categories: Other subtasks or Form subtasks. Understanding the difference is key to designing tasks that are clear and efficient for your customers. This video walks through both types, their step options, and how conditional logic works differently between them.

What You'll Learn

This video is a reference walkthrough of the two subtask type categories in the task builder. After watching, you'll know exactly which type to use when designing tasks — and how branching/conditional logic works for each.

The Two Subtask Types

1⃣ Other Subtasks — Single-Action Steps

Other subtasks are the most basic subtask type. Each one is a single, standalone step — the step itself is the subtask, with no additional steps nested inside it. After completing an Other subtask, the customer clicks Save and Continue to move to the next one.

Step types available as Other subtasks include:

• Yes/No question

• Multi-choice question (single or multiple selection)

• Dropdown

• Share a video

• Embeddable (iFrame/URL embed)

• Adobe e-Sign

Other subtasks are best suited for simple tasks where each step is a discrete action and you don't need to group multiple inputs together.

Branching with Other Subtasks

Conditional branching for Other subtasks happens between subtasks in the tree view. For example, if you add a multi-choice question with several options, each option can branch to a different path — meaning customers who select different answers will see different subsequent subtasks. This is how you create personalized, adaptive task flows without building separate tasks for each scenario.

2⃣ Form Subtasks — Multi-Input Containers

A Form subtask is a container that holds multiple steps inside a single subtask. The customer completes all of the inputs inside the form before clicking Save and Continue — they don't save between each individual step. This is useful when you need to collect several related pieces of information at once (e.g., a name, a department selection, and a file upload), without making the customer click through multiple separate subtasks.

Example inputs you can add inside a Form subtask:

• Text input

• Dropdown

• Request file (file upload)

• Single choice / multi-choice

• Table (for multi-row data entry)

• And more

Branching Inside Form Subtasks

Conditional logic for Form subtasks works differently than for Other subtasks — branching happens inside the subtask, not between subtasks in the tree view. For example, you can configure a single-choice step within a form so that selecting a particular option shows or hides other fields within that same form. This keeps the form dynamic and relevant without adding more subtasks to the tree.

Quick Reference

In the next video, we'll go deeper into the specific step types you can add inside Form subtasks and how to use them.

📺 Continue learning: Visit the OnRamp Tutorials YouTube Playlist for the full collection of video walkthroughs.