Data Binding
Bind data from your Looply Workflow directly into your Adaptive Card.
The data binding feature from the Adaptive Card designer allows the binding of any JSON attribute from the Sample Data Editor to an element on an Adaptive Card.
Linking a Workflow to an Adaptive Card
When adding an Adaptive Card to a Workflow, if you click "Create new card" this will create a new Card but will also link the Workflow Schema to the Adaptive Card allowing you to bind for example the result from an API request to a TextBlock on your Adaptive Card. Find a more in-depth explanation from the Using Integrations Section or check out Chapter 1 of our Building Adaptive Cards tutorial.
Simple Data Binding
Whilst in the Adaptive Card Designer you will notice a Sample Data Editor, this holds the data that can be bound to the Adaptive Card you are creating. Data can be added to this code editor or it can be pulled from the workflow schema where this card is bound. Below is a sample Sample Data Editor that takes data from a Workflow Schema:
{
"payload": {
"output": {
"workflow_version": "1",
"workspace_id": "****",
"workflow_process_id": "****",
"workflow_id": "****",
"looply_sap_profile_settings": {
"requires_sap_profile": false
},
"executor": "****",
"organization_id": "****",
"workflow_execution_id": "****",
"workflow_trigger_type": "REQUEST"
},
"description": "Request"
},
"WorkflowStartState": null,
"function_1": {
"output": "hello world",
"description": "My Function"
}
}Data binding can be done on a wide variety of properties ranging from the Text property of a TextBlock to the choices of an Input.ChoiceSet.
Binding data from the Sample Data Editor is easy. You can do it via any of these 3 ways:
When an element on the Adaptive Card Canvas has been selected, some elements like the TextBlock will show you a "Bind..." button. Clicking on this will pull up a dropdown menu showing you all the attributes you can bind to the TextBlock. This dropdown is generated via the data supplied in the Sample Data Editor.
When an element on the Adaptive Card Canvas has been selected, the Element Properties Toolbar should have all the customisation options for the respective field. Notice that certain fields have a button displaying "...", clicking on this will pull up a dropdown menu showing you all the attributes you can bind to this particular property. Like option 1, this dropdown is generated via the data supplied in the Sample Data Editor.
You can manually type in the binding directly into the Card Payload Editor.
Note: Please note that if a binding is incorrectly typed directly into the Card Payload Editor, the adaptive card canvas may not appear.
Binding will appear in the Card Payload Editor as shown below:
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"body": [
{
"type": "TextBlock",
"wrap": true,
"text": "${$root.payload.output.workflow_id}" // data binding
}
],
"version": "1.5"
}Note: Manually typing in data bindings must follow the above syntax.
Binding JSON Arrays
Data in our Sample Data Editor may contain arrays of strings or arrays of JSON objects. Binding these structures to our Adaptive Card is a little different from the above Simple Data Binding which follows a more one-to-one approach.
Note: Manually typing data bindings from an array is highly advised. Using the Element Properties Toolbar will result in incorrect mappings for array items.
If the data within the Sample Data Editor looked as follows:
{
"payload": {
"output": {
"process_id": "****",
"workflow_id": "****",
"workflow_execution_id": "****",
"version": "5",
"scenario_id": "****",
"workflow_version": "1",
"workspace_id": "****",
"util_data": [ // array of JSON objects to bind
{
"title": "Claim not approved",
"value": "1"
},
{
"title": "Query with claim",
"value": "2"
},
{
"title": "Incorrect grade / SCP claimed",
"value": "3"
},
{
"title": "Incorrect payment type claimed",
"value": "4"
}
],
"organization_id": "****",
"workflow_trigger_type": "REQUEST",
"recipient": "[email protected]",
"step": "****"
},
"description": "Request"
}
}Displaying Singular Items.
Displaying only the 3rd title from our util_data array is straightforward and replicates process 3 from Simple Data Binding.
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"wrap": true,
"text": "${$root.payload.output.util_data[2].title}" // data binding
}
]
}Displaying Lists
If we want to display a TextBlock for each of the title values in our util_data array we need to manually type this binding into our Card Payload Editor against our TextBlock. A "data context" has to be established on our TextBlock - this means that the TextBlock is only observing data within a certain attribute within our Sample Data Editor. Due to a data context being applied to the TextBlock, our binding will appear shorter than the above Simple Data Binding approach. Below is how we can display 8 TextBlocks, where each element points to a different title in our util_data array.
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [
{
"type": "TextBlock",
"wrap": true,
"$data": "${$root.payload.output.util_data}", // data context
"text": "${title}" // data binding
}
]
}Using JSON Arrays in Input.ChoiceSets
You can bind data directly to the choices attribute of an Input.ChoiceSet. This is particularly useful if the choices are dynamic and could change.
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [
{
"type": "Input.ChoiceSet",
"choices": "${$root.payload.output.util_data}", // data binding
"placeholder": "Choices"
}
]
}Last updated