Label and Variables

In Clappia, every field block added to an app has two key identifiers: a Label and a Variable Name. Understanding the difference and how each is used is important for building dynamic, functional apps especially when working with formulas, workflows, conditions, statuses and PDFs.

‍

Label

The Label is the name shown to the user in the app interface. It tells the user what kind of input is expected.

• Example: If you add a field (single selector block) to collect a user's approval, you might set the label as "Approval Needed?"

• This label appears exactly as entered to the end user when they open the app to make a submission.
  

Variable Name

Once you save the block after assigning it a label, Clappia automatically generates a Variable Name for that block. This variable acts as a unique reference to the block’s value when writing logic, calculations, workflows, and more.

• For example, if the block label is "Approval Needed?", the variable might be automatically generated as {approval_n}.
  
  
• You can edit this to something cleaner like {approval} from the right-hand configuration panel before or after saving the block.
  

• The final variable name appears above the block when in Design App view.
  

Multiple Blocks with the Same Label

If you use the same label for multiple blocks (like two fields named "Approval"), Clappia automatically appends numbers to the variable names to differentiate them such as {approval_1} and {approval_2}.

Why Use Variable Names

Variable names are used to pull the actual field values submitted by users and apply them in various parts of your app. They’re essential for making your app dynamic and functional.

Here’s how you can use them:

1. In Calculations

If your app includes fields like Quantity and Price, you can use a Formula block to calculate the total cost.

• Example: Add a Formula block and enter {quantity} * {price} in the right-hand panel.
  

• To select fields, type @ followed by the field name. A dropdown will appear with all available field variables.
  

Clappia supports spreadsheet-like functions, so you can build complex calculations using these variable names instead of cell numbers.

2. In Display Conditions

Variable names can be used in the Display this field if setting to show or hide blocks based on user inputs.

• Example: Show a "Corrective Actions" field only if {approval} = "No".
  

Display conditions also support spreadsheet logic functions like IF, AND, OR, etc.

You can also apply conditions to entire sections using variables, giving you full control over what the user sees at different stages.

3. In Workflows

Variable names play a major role in workflows to personalize logic and automate actions:

• Email Workflow: You can use {email} in the “To” field to send an email to the address entered by the user in the app.
  
  
• IF Workflow Node: You can define conditions like {approval} = "Yes" to trigger different branches of a process.
  
  

This makes workflows dynamic and based on actual data filled in the app.

4. In PDFs

You can reference any field's variable name to display its submitted value in a PDF template.

• Example: Use {product}, {quantity}, and {price} to populate product details in an invoice-style PDF.
  

This lets you auto-generate formatted documents using real-time data from the app.

5. In Copyable Sections

Copyable sections allow you to dynamically duplicate a group of blocks. Useful for repeating data like multiple products in an order form.

Each copied block will generate its own variable name (e.g., {product#1}, {product#2}), which can be used for workflows and PDFs.

• Example: If you're generating an invoice, you can use these variables to list multiple products and calculate totals accordingly.
  

System Variables vs User-Defined Variables

While user-defined variables are tied to specific blocks (like {approval}), Clappia also provides system variables such as:

• {$status} – The current status of a submission (e.g., “Submitted”, “L1 Approved”).
  
  
• {$submissionId} – A unique identifier for each submission.
  
  

These variables are predefined by Clappia and help control logic based on system-level information. They’re especially useful in workflows, display conditions, and audit tracking.

‍

Labels guide the user, variable names drive the logic behind the scenes.

Understanding how and where to use variable names unlocks the full potential of Clappia’s features, from logic-based display rules to automated workflows and custom document generation.

‍