Last updated: 03 January 2023

You can use templating to dynamically create any of our composer types. In this doc, we cover the values each of our composer types needs to contain to work appropriately.

type always takes the value of the composer you are building. For example, to build a message composer, you will enter "Type": "Standard", for a fuzzy, "Type": "fuzzy", etc.

Composer

Template

Values

Message

{
    "type": "message",
    "content": {
      "placeholder": "Send 
        a message",
      "disabled": false
    }
}
CODE

  • placeholder: text string, up to 255 characters.

  • disabled: true or false.

Fuzzy

{
    "type": "fuzzy",
    "content": {
      "placeholder": "Choose 
        an option...",
      "multi': false,
      "items": [
        {"label": "", 
          "value": ""}
      ]
    } 
}
CODE

  • placeholder: text string, up to 255 characters.

  • disabled: true or false.

  • multi: true or false.

  • items: array, minimum 1, maximum 1,000.

  • item label: text string, up to 255 characters.

  • item value: text string, up to 255 characters.

Numeric

{
    "type": "numeric",
    "content": {
      "placeholder": "Enter 
        a number...",
      "disabled": false
    } 
}
CODE

  • placeholder: text string, up to 255 characters.

  • disabled: true or false.

Date

{
    "type": "date",
    "content": {} 
}
CODE

  • content: must be {}

Time

{
    "type": "time",
    "content": {} 
}
CODE

  • content: must be {}

Date time

{
    "type": "date-time",
    "content": {} 
}
CODE

  • content: must be {}

Deactivated

{
    "type": "deactivated",
    "content": {} 
}
CODE

  • content: must be {}

Feedback

{
    "type": "feedback",
    "content": {} 
}
CODE

  • content: must be {}

Hidden

{
    "type": "hidden",
    "content": {} 
}
CODE

  • content: must be {}

Auth

{
    "type": "auth",
    "content": {} 
}
CODE

  • content: must be {}