Use task modules in tabs

Add a task module to your tab to simplify your user's experience for any workflows that require data input. Task modules allow you to gather their input in a Microsoft Teams-Aware pop-up. A good example of this is editing Planner cards. You can use task modules to create a similar experience.

To support the task module feature, two new functions are added to the Teams JavaScript client library. The following code shows an example of these two functions:

    taskInfo: TaskInfo,
    submitHandler?: (err: string, result: string | any) => void
): void;

    result?: string | any,
    appIds?: string | string[]
): void;

You can see how invoking a task module from a tab and submitting the result of a task module works.

Invoke a task module from a tab

To invoke a task module from a tab use microsoftTeams.tasks.startTask() passing a TaskInfo object and an optional submitHandler callback function. There are two cases to consider:

  • The value of TaskInfo.url is set to a URL. The task module window appears and TaskModule.url is loaded as an <iframe> inside it. JavaScript on that page calls microsoftTeams.initialize(). If there's a submitHandler function on the page and there's an error when invoking microsoftTeams.tasks.startTask(), then submitHandler is invoked with err set to the error string indicating the same. For more information, see task module invocation errors.
  • The value of taskInfo.card is the JSON for an Adaptive Card. There's no JavaScript submitHandler function to call when the user closes or presses a button on the Adaptive Card. The only way to receive what the user entered is by passing the result to a bot. To use an Adaptive Card task module from a tab, your app must include a bot to get any response from the user.

The next section gives an example of invoking a task module.

Example of invoking a task module

The following image displays the task module:

Task Module Custom Form

The following code is adapted from the task module sample:

let taskInfo = {
    title: null,
    height: null,
    width: null,
    url: null,
    card: null,
    fallbackUrl: null,
    completionBotId: null,

taskInfo.url = "";
taskInfo.title = "Custom Form";
taskInfo.height = 510;
taskInfo.width = 430;
submitHandler = (err, result) => {
    console.log(`Submit handler - err: ${err}`);
    console.log(`Submit handler - result\rName: ${}\rEmail: ${}\rFavorite book: ${result.favoriteBook}`);
microsoftTeams.tasks.startTask(taskInfo, submitHandler);

The submitHandler is simple and it echoes the value of err or result to the console.

Submit the result of a task module

The submitHandler function resides in the TaskInfo.url web page and is used with TaskInfo.url. If there's an error when invoking the task module, your submitHandler function is immediately invoked with an err string indicating what error occurred. The submitHandler function is also called with an err string when the user selects X at the upper right of the task module to close it.

If there's no invocation error and the user doesn't select X to dismiss it, the user chooses a button when finished. Depending on whether it's a URL or an Adaptive Card in the task module, the next sections provide details on what occurs.

HTML or JavaScript TaskInfo.url

After validating the user's inputs, call the microsoftTeams.tasks.submitTask() function referred to as submitTask(). Call submitTask() without any parameters if you just want Teams to close the task module. You can pass an object or a string to your submitHandler.

Pass your result as the first parameter. Teams invokes submitHandler where err is null and result is the object or string you passed to submitTask(). If you call submitTask() with a result parameter, you must pass an appId or an array of appId strings. This permits Teams to validate that the app sending the result is same as the invoked task module.

Adaptive Card TaskInfo.card

When you invoke the task module with a submitHandler and the user selects an Action.Submit button, the values in the card are returned as the value of result. If the user selects the Esc key or X at the top right, err is returned instead. If your app contains a bot in addition to a tab, you can include the appId of the bot as the value of completionBotId in the TaskInfo object. The Adaptive Card body as filled in by the user is sent to the bot using a task/submit invoke message when the user selects an Action.Submit button. The schema for the object you receive is similar to the schema you receive for task/fetch and task/submit messages. The only difference is that the schema of the JSON object is an Adaptive Card object as opposed to an object containing an Adaptive Card object as when Adaptive cards are used with bots.

The following is the example of payload:

  "task": {
    "type": "continue",
    "value": {
      "title": "Title",
      "height": "height",
      "width": "width",
      "url": null,
      "card": "Adaptive Card or Adaptive Card bot card attachment",
      "fallbackUrl": null,
      "completionBotID": "bot App ID"

The following is the example of Invoke request:

let taskInfo = {
    title: "Task Module Demo",
    height: "medium",
    width: "medium",
    card: null,
    fallbackUrl: null,
    completionBotId: null,

taskInfo.card = {
    "type": "AdaptiveCard",
    "$schema": "",
    "version": "1.4",
    "body": [
            "type": "TextBlock",
            "text": "This is sample adaptive card.",
            "wrap": true

submitHandler = (err, result) => {
    console.log(`Submit handler - err: ${err}`);
        "Result = " + JSON.stringify(result) + "\nError = " + JSON.stringify(err)

microsoftTeams.tasks.startTask(taskInfo, submitHandler);

The next section gives an example of submitting the result of a task module.

Example of submitting the result of a task module

For more information, see the HTML form in the task module. The following code gives an example of where the form is defined:

<form method="POST" id="customerForm" action="/register" onSubmit="return validateForm()">

There are five fields on this form but for this example only three values are required, name, email, and favoriteBook.

The following code gives an example of the validateForm() function that calls submitTask():

function validateForm() {
    var customerInfo = {
        name: document.forms["customerForm"]["name"].value,
        email: document.forms["customerForm"]["email"].value,
        favoriteBook: document.forms["customerForm"]["favoriteBook"].value
    microsoftTeams.tasks.submitTask(customerInfo, "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx");
    return true;

The next section provides task module invocation problems and their error messages.

Task module invocation errors

The following table provides the possible values of err that can be received by your submitHandler:

Problem Error message that is value of err
Values for both TaskInfo.url and TaskInfo.card were specified. Values for both card and URL were specified. One or the other, but not both, are allowed.
Neither TaskInfo.url nor TaskInfo.card specified. You must specify a value for either card or URL.
Invalid appId. Invalid app ID.
User selected X button, closing it. User canceled or closed the task module.

Code sample

Sample name Description .NET Node.js Manifest
Task module sample bots-V4 This sample shows how to create task modules using bot framework v4 and teams tabs. View View View

Next step

See also