Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.penbox.io/llms.txt

Use this file to discover all available pages before exploring further.

The Number field captures numeric values — integers or decimals — with optional formatting and validation. Number fields enable calculations, comparisons, and numeric operations within automations and data processing. Use Number fields whenever you need to perform mathematical operations, apply min/max validation, or format values with prefix/suffix. Number fields are essential for quantities, ages, scores, and any data that requires numeric processing.

​
When to Use

Use Number fields for:
  • Quantities (items, count, volume)
  • Ages and years
  • Scores and ratings
  • Percentages and ratios
  • Measurements (weight, height, distance)
  • Identifiers that are purely numeric (account numbers, IDs)
  • Calculated values
Consider alternatives:
  • Use Currency for monetary amounts (prices, costs, revenues, claims)
  • Use Text for alphanumeric IDs (contain letters)
  • Use Choices for predefined numeric ranges (age groups, price tiers)
  • Use Date for years that represent dates

​
Configuration Options

OptionDescriptionTypeDefaultExample
keyUnique identifierStringRequirednumber_of_employees
nameDisplay labelStringRequired”Number of Employees”
descriptionHelp text for usersStringOptional”Total full-time employees”
minMinimum allowed valueNumberNone0
maxMaximum allowed valueNumberNone1000000
decimalsNumber of decimal placesNumberNone2
prefixText displayed before the valueStringNone$
suffixText displayed after the valueStringNonekg
placeholderHint text shown in empty fieldStringNone”Enter a number”
visibilityDisplay settingStringalways-visiblehide-when-empty
sectionSection this field belongs toStringNoneSection UUID

​
Examples

​
Basic Integer

Collect a simple count: 
{
  "key": "number_of_employees",
  "type": "number",
  "name": "Number of Employees",
  "description": "Total full-time employees",
  "min": 1
}

​
Decimal Value

Collect precise measurements: 
{
  "key": "weight_kg",
  "type": "number",
  "name": "Weight (kg)",
  "description": "Weight in kilograms",
  "decimals": 2,
  "suffix": "kg",
  "min": 0
}

​
Percentage with Prefix/Suffix

Collect a percentage value: 
{
  "key": "completion_percentage",
  "type": "number",
  "name": "Completion Percentage",
  "description": "Project completion percentage",
  "suffix": "%",
  "min": 0,
  "max": 100,
  "decimals": 1
}

​
Validation

Number fields enforce numeric validation automatically:

​
Type Validation

  • Only numeric values accepted
  • Decimals allowed based on decimals configuration
  • Non-numeric input rejected

​
Range Validation

  • min - Minimum allowed value (inclusive)
  • max - Maximum allowed value (inclusive)
  • User cannot enter values outside range

​
Decimal Validation

  • decimals defines maximum decimal places allowed
  • For integers: omit decimals or set to 0
  • For precise values: set decimals to the required precision (e.g., 2)
Validation happens when users fill the field. Existing data or API imports are not automatically validated.

​
Best Practices

Always use Number for numeric data:
  • Don’t store numbers as text (prevents calculations)
  • Use Number even if you don’t need calculations now (future-proofs)
  • Enables numeric comparisons in automations
Set appropriate min/max:
  • Prevents invalid or unrealistic values
  • Catches data entry errors
  • Useful for regulated fields with limits
Configure decimals based on needs:
  • Omit decimals for counts and quantities
  • Use 2 for precise measurements
  • Use appropriate precision for your domain
Use prefix/suffix for display context:
  • Add suffix: "kg" for weight fields
  • Add suffix: "%" for percentage fields
  • Helps users understand expected format
Use Currency for monetary values:
  • Don’t use Number with a currency prefix for financial amounts
  • The Currency field type is purpose-built for monetary values
Validate reasonably:
  • Don’t set overly restrictive min/max
  • Consider edge cases (zero values, large amounts)
  • Test with realistic data ranges

Currency

Use for monetary amounts with currency formatting

Text

Use for alphanumeric IDs and formatted numbers

Choices

Use for predefined numeric ranges or tiers

Data Schema Overview

Back to Data Schema overview