Skip to main content
These entities cover inputs that go beyond simple text and numbers. Use them to collect documents, schedule dates, and capture addresses or property details. They are especially useful for financial services where validated data is critical.

​
File Upload

File Upload

When to use: Collect documents, photos, or ID scans
What users see: A secure upload field with size and type checks
Tips:
  • Tell users what file types you accept (e.g. PDF, JPG)
  • Keep size limits clear up front
  • Allow users to remove and replace files easily

​
Showing Uploaded Files on a Live Page

Files a customer uploads in a chatflow can be listed on a live page for viewing or download. A file is served from the Wizflow app at /api/files/<file name>; add ?download=1 to make the browser save it instead of opening it. Only the logged-in customer who uploaded the file can fetch it, so a “your uploaded files” page is safe to build.

Uploading a file in a chatflow, then listing it with a download button on a live page

Build the link in a web component block and insert the file name from the upload entity’s response as a resource. Anyone else who opens the link gets an unauthorised response, not the file.

​
Date Picker

Date Picker

When to use: Birth dates, policy start dates, appointments
What users see: A calendar interface with optional restrictions
Tips:
  • Use for clear, single dates — avoid long multi-date selections
  • Add limits if needed (e.g. minimum age, max booking window)
  • Keep formats consistent across your flows

​
Address & Location

Address

When to use: Collecting validated Danish addresses
What users see: Real-time suggestions as they type, powered by RTB

Household House

When to use: Mortgage, insurance, or property flows
What users see: A structured form for property value, ownership, and loans
Tips:
  • RTB-powered lookups ensure addresses are accurate and reduce manual typing
  • Use Household House only when you need detailed property data
  • Combine with Choice or Amount entities for financial scenarios

​
Best Practices

  • Be clear: Tell users exactly what you need (file type, date range, address format)
  • Validate gently: Prevent obvious errors but don’t overwhelm with restrictions
  • Keep it relevant: Only show these fields when they’re truly needed
  • Mobile friendly: Make sure uploads, calendars, and address inputs work well on small screens

​
Example Recipes

Insurance application
Message → Date Picker (Birth date) → Address → File Upload (Documents) Mortgage application
Message → Household House (Property details) → Amount (Loan) → File Upload (Supporting docs)