Search⌘K

What is the Input Portal and how do I get started?

A short orientation to the Input Portal with links to the full guides.

The Input Hub (also called the Input Portal) is where ZiplineOS deals come to life. It is the one place where you design the questions you ask applicants (forms), build the step-by-step process every application follows (workflows), and watch real applications move through that process from first enquiry to settlement.

Four concepts cover everything:

  • Form — collects answers (a reusable list of questions).
  • Workflow — defines the journey: an ordered set of steps shown as columns on a board.
  • Deal — one real application moving through a workflow.
  • Workflow Items — the things that happen inside each step (fill a form, run a check, collect signatures).

You design forms and workflows once; deals are the live copies that follow them. Because the same forms feed both the internal portal and what applicants fill out, you only ever define something once — change a question and it changes everywhere.

Who uses it

Brokers and team members author forms and workflows, create and run deals, fill in data, chase documents, and move deals forward. Platform admins also curate the shared library of ready-made packs.

Applicants never see the Input Hub. They receive a secure "magic link" by email that opens only their part of the application in a separate portal called Collect — just the form or document they need to complete.

How to get started

  1. Read How to Use the Input Portal — walks one real mortgage application from enquiry to settlement.
  2. Read Order Workflows & Workflow Items when you are ready to build a process.
  3. Use Forms & Fields and Validations to build your first form field by field.

You don't have to start blank. Platform admins curate packs — ready-made bundles of forms and workflows — that you can install in one click and then adjust.

Internal teams also have access to a hands-on getting-started tutorial and a full technical reference for the Input Hub (routes, entities, API endpoints). Both are available to staff with internal or technical space access — ask an admin if you need them.

Where to learn more