Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Input.Text
  • Input.Date
  • Input.Time
  • Input.Number
  • Input.ChoiceSet
  • Input.Toggle
  1. Adaptive Cards
  2. Building Adaptive Cards

Input Elements

Adaptive Cards that act as Forms to retrieve data from an end user.

PreviousContent ElementsNextActions

Last updated 1 year ago

Input.Text

Description

A standard input field that will allow users to type in text. This input can be assorted with a Label and Placeholder.

Regex validation is supported on this field to validate inputs. If validation fails the error message is then shown.

This Input can have an Inline Action where the user can submit the data from this input field straight back to Looply for processing.

You can change this input to a multi-line input field where a larger response can be retrieved.

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of first_name and an input field value of John will be passed to Looply as {"first_name": "John"}.

All of the above is edited using the that is found when clicking on the respective Input.Text field.

Technical Documentation

Input.Date

Description

A field designed for taking in dates from the end user.

Provides a calendar for the end user to select a date.

This input can be assorted with a Label and a Default value.

All Dates added must follow the YYYY-MM-DD standard.

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of date and an input field value of 2023-10-17 will be passed to Looply as {"date": "2023-10-17"}.

Technical Documentation

Input.Time

Description

A field designed for taking in times from the end user.

This input can be assorted with a Label and a Default value.

All Times added must follow the MM:HH standard.

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of time and an input field value of 15:30 will be passed to Looply as {"time": "15:30"}.

Technical Documentation

Input.Number

Description

A field designed for taking in numbers from the end user.

This input can be assorted with a Label, placeholder, and a Default value.

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of price and an input field value of 1.10 will be passed to Looply as {"price": "1.10"}.

Technical Documentation

Input.ChoiceSet

Description

A field designed to replicate a dropdown menu.

This input can be assorted with a Label, placeholder, and a Default value.

  • Compact

    • Follows the same style as a regular dropdown menu.

  • Expanded

    • Changes the ChoiceSet into radio buttons or checkboxes depending on if multi-selection is selected.

  • Filtered

    • Changes the ChoiceSet to appear as an Input.Text field but will autocomplete values if the user starts to type a value from the ChoiceSet array.

Applying the Multi-Selection option to the ChoiceSet will always change the ChoiceSet into a group of checkboxes where each checkbox points to a choice.

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of choice and an input field value of 1 will be passed to Looply as {"choice": "1"}.

Technical Documentation

Input.Toggle

Description

Input to replicate a checkbox.

This input can be assorted with a Label, a Title, and a Default value

Labels will go above the checkbox whilst Titles will go to the side.

Specific values can be assigned when the Toggle has been toggled "On" or "Off"

Applying an Id to this input field will mean the data passed to Looply will be attributed to it. e.g An Id of toggle and an input field value of true will be passed to Looply as {"toggle": "true"}.

Technical Documentation

You can supply a Min and a Max value for validation where if the user incorrectly adds a date will show the error message that is specified in the respective .

All of the above is edited using the toolbar that is found when clicking on the respective Input.Date field.

You can supply a Min and a Max value for validation where if the user incorrectly adds a time will show the error message that is specified in the respective .

All of the above is edited using the that is found when clicking on the respective Input.Time field.

You can supply a Min and a Max value for validation where if the user incorrectly adds a number will show the error message that is specified in the respective .

All of the above is edited using the that is found when clicking on the respective Input.Number field.

If a user incorrectly selects or types a value not within the ChoiceSet scope of values then an error is shown. That error message is customised via the .

There are a few different types of ChoiceSet: Compact, Expanded, and Filtered. This can be changed from the using the Style property.

All of the above is edited using the that is found when clicking on the respective Input.ChoiceSet field.

All of the above is edited using the that is found when clicking on the respective Input.Toggle field.

Read more about Input.Date
Read more about Input.Time
Read more about Input.Number
Read more about Input.ChoiceSet
Read more about Input.Toggle
This can be any of the Actions from the Action section.
Read more about Input.Text
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar
Element Properties Toolbar