Skip to content

Adaptive Card

This Action Type allows the AI Agent to present information in a structured, interactive card format using the Adaptive Card framework. You can define the card layout in JSON, reuse captions for consistent labels or localization, and reference memory parameters to display dynamic data from integrations

Step 1. Create an Adaptive Card Action by pressing the button at the bottom of an Action Group:

Screenshot

Step 2. A new Adaptive Card Action will appear and be ready to be filled in. Let’s set up this block step by step.

Screenshot

A – Help Dialog

For guidance on the action setup, click the Information Icon. A help dialogue with instructions will appear.

B – Adaptive Card JSON Editor

In the JSON Editor section, you paste the Adaptive Card schema that defines:

  • Layout (columns, containers, text blocks, images, etc.)
  • Styles (size, weight, color of text)
  • Interactive elements (buttons, inputs, toggles, etc.)

You can use the official Adaptive Card Designer to visually create cards and then copy the JSON output.

C – Set Captions

Captions are static, reusable text labels you define once and then reference inside your card JSON. They’re there to keep your card consistent and to make it easier to translate or update labels without touching the card JSON every time.

Add captions in the JSON array format:
[“caption text 1″,”caption text 2”, …]

You can reference captions in the Adaptive Card structure using:

  • ${captions[n]} – for non-repeating sections
  • ${$root.captions[n]} – for repeated blocks (e.g., items in a list)

D – Select Data Source Memory Parameter
If your Adaptive Card displays data received from an integration, define the memory parameter as the data source here.

Use the following format to reference values:
${memory_parameter}

E – Define Notification Mode

Enable Send as Notification option if you want the message to be sent as a notification to a selected recipient.

Recipient
Use a reference value that contains a recipients list. Example: {{memory.rt_recipients_list}}

In this example, we will create a Vendor Open Items Search Card.

Step 1. Open the Adaptive Card Designer and design your card layout.

Screenshot

Step 2. Once the card is ready, copy its structure and paste it into the Adaptive Card JSON Editor.

Screenshot

Input example:

Show Adaptive Card JSON
{
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.6",
"body": [
{
"type": "Container",
"items": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"text": "${captions[0]}",
"wrap": true,
"size": "Large",
"weight": "Bolder",
"color": "Default",
"horizontalAlignment": "Center"
}
]
}
]
}
]
},
{
"type": "Container",
"items": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"text": "${captions[1]}",
"wrap": true,
"weight": "Bolder"
}
]
},
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "TextBlock",
"text": "{{memory.rt_ppp_vendor_name}}",
"wrap": true,
"weight": "Bolder"
}
]
}
]
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "Input.ChoiceSet",
"choices": [
{
"$data":"${rt_fmd_co_code.company_codes}",
"title": "${text}",
"value": "${id}"
}
],
"label": "${captions[2]}",
"style": "filtered",
"id": "rt_fmd_company_code",
"value": "{{memory.rt_fmd_company_code}}"
}
]
}
]
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "Input.Date",
"id": "rt_ppp_voi_date_from",
"label": "${captions[3]}",
"value": "${formatDateTime(utcNow(), 'yyyy-MM-dd')}"
}
]
}
],
"spacing": "Small"
},
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": "stretch",
"items": [
{
"type": "Input.Number",
"placeholder": "${captions[4]}",
"label": "${captions[5]}",
"id": "rt_number_of_hints",
"value": 100,
"min": 1,
"max": 100,
"isRequired": true,
"errorMessage": "${captions[6]}"
}
]
}
]
}
]
},
{
"type": "ActionSet",
"actions": [
{
"type": "Action.Submit",
"title": "${captions[7]}",
"id": "GenericAction"
}
]
},
{
"type": "Input.Text",
"id": "AdditionalData",
"value": "{\"message\": \"${captions[8]}\"}",
"isVisible": false
}
]
}

Step 3. Define captions for static labels and references.

Screenshot

Input example:

[“Vendor’s Open Items Search”,”Display for vendor: “,”Company Code”,”Open at key date”,”Enter maximum No. of hits”,”Maximum No. of Hits (limited by 100)”,”Number of hits is mandatory”,”Search”,”Search”]

Step 4. Select the Data Source Memory Parameter if your card uses dynamic values from integrations.

Screenshot

Input example: rt_fmd_co_code

Step 5. Save your entries.

Step 6. Preview the card to confirm everything renders as expected.

Screenshot

In the FLP Chat, a card keeps the values the user entered after they submit it. The card stays in the conversation with those values, so the user can see later which selection the answer below it is based on.

When the user fills in the card and presses a submit button:

  • The values the user entered stay in the card’s fields.
  • The card’s submit buttons are hidden, so the same card cannot be sent twice. Buttons that only switch between pages of a card (Action.Submit with a page value in its data) stay visible.
  • The submitted card is saved with the conversation. It shows the same values after the user reloads the page, or closes and opens the chat again.

For example, the user selects the filters of a Purchase Order Search card and presses Search:

The Purchase Order Search card in the FLP Chat before submitting, with the filters filled in and the Search button at the bottom

After the search, the card still shows the selected document type, the checkbox and the dates, the Search button is gone, and the result follows below the card:

The same card after submitting: the selected values are kept, the Search button is hidden, and the search results appear below

You do not need to change anything in the card JSON for this. Each input must have an id, as the Adaptive Card framework requires for its value to be submitted.