Button in the Task Automation Rules Designer TASK_ROBOT_DESIGNER_TOOLBAR

Choose a tool for developing with an AI agent:

  • use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
  • use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: placement, task

The widget adds its own button to the task automation rules designer. The handler receives the context of the automation the widget is opened from: the personal planner of a user or a project. The personal planner is a user's task list. The automation rules designer for the personal planner is opened from this list.

This placement is chosen when an application extends task automation: to build your own scenario designer, to carry over rules from an external system, or to add a setting that is missing among the standard automation rules. The button opens the application interface but does not register an automation step of its own.

The placement code is specified in the PLACEMENT parameter of the placement.bind method.

The widget is not displayed in the interface until the application installation is complete. Check the application installation

Where the Widget is Embedded

Placement Code

Location

TASK_ROBOT_DESIGNER_TOOLBAR

Button in the task automation rules designer

Where to Find It in the Interface

Open the task list of a user or a project and click Automation rules. The application button appears on the right in the header of the Task automation window. If the button carries the name of another item, click the arrow next to it: the application item is in the dropdown menu.

Button in the task automation rules designer

When the designer is opened from a project, the SONET_GROUP_ROBOT_DESIGNER_TOOLBAR placement is rendered in the same menu. It is a separate placement with its own sonet_group scope and a separate call context. It is absent in the automation of a personal planner: a personal planner has no group.

What the Handler Receives

Data is sent in a POST request: some parameters come in the handler URL query string, the rest in the request body

The example is shown for the automation of a project. In the automation of a personal planner, the set of standard parameters is the same. Only the context key in PLACEMENT_OPTIONS changes: USER_ID arrives instead of GROUP_ID.


        Array
        (
            [DOMAIN] => xxx.bitrix24.com
            [PROTOCOL] => 1
            [LANG] => en
            [APP_SID] => 4617fa96af5d1f523fc2e2b72bd54f11
            [AUTH_ID] => 5253ba6600705a0700005a4b00000001f0f1076fef51e6d3d3c1616a9fd92a71
            [AUTH_EXPIRES] => 3600
            [REFRESH_ID] => 42d2e16600705a0700005a4b00000001f0f107cf69d8060249da353587f8ec86
            [SERVER_ENDPOINT] => https://oauth.bitrix.info/rest/
            [APPLICATION_TOKEN] => 3f0a7c19e5b84d2196c8ad470e5f2b31
            [APPLICATION_SCOPE] => task,placement
            [member_id] => da45a03b265edd8787f8a258d793cc5d
            [status] => L
            [PLACEMENT] => TASK_ROBOT_DESIGNER_TOOLBAR
            [PLACEMENT_OPTIONS] => {"GROUP_ID":"11","URI":"\/workgroups\/group\/11\/tasks\/"}
        )
        
        

After parsing, the PLACEMENT_OPTIONS string from this example looks like this:

{
            "GROUP_ID": "11",
            "URI": "/workgroups/group/11/tasks/"
        }
        

Required parameters are marked with *

Parameters in the Handler URL Query String

Parameter
type

Description

DOMAIN*
string

The Bitrix24 address where the widget handler was invoked

PROTOCOL*
string

Secure or non-secure HTTP protocol:

  • 0 - HTTP
  • 1 - HTTPS

LANG*
string

The user interface language of Bitrix24 that invoked the widget. You can localize the interface language in your widget based on this value

APP_SID*
string

Application session identifier. Bitrix24 generates a new one each time the widget is rendered and uses it to link the js library with the application environment

Parameters in the POST Request Body

Parameter
type

Description

AUTH_ID
string

Authorization token OAuth 2 issued for the user who invoked the widget. Can be used for REST API calls on behalf of this user

AUTH_EXPIRES
integer

Time in seconds after which the authorization token will become invalid

REFRESH_ID
string

Refresh token OAuth 2 issued for the user who invoked the widget. Can be used to refresh the authorization token on behalf of this user

SERVER_ENDPOINT*
string

Address of the Bitrix24 authorization server needed to refresh OAuth 2 tokens

APPLICATION_TOKEN*
string

Application token. The same value is passed in the application_token parameter when event handlers are invoked. The widget handler can use it to verify that the request came from Bitrix24

APPLICATION_SCOPE*
string

List of scopes granted to the application, separated by commas. Shows which REST API methods are available with the authorization token received

member_id*
string

Unique string identifier of Bitrix24 where the widget handler was invoked.

status
string

Type of application that registered the handler for this widget. Accepts values:

  • L - local application
  • F - free mass-market application
  • D - demo version of a mass-market application
  • T - trial version of a mass-market application, time-limited
  • P - paid mass-market application

PLACEMENT*
string

The placement code. You can use the same handler URL for all your widgets. The value that Bitrix24 will report in the PLACEMENT parameter will help determine from which specific placement your handler was invoked in each case

PLACEMENT_OPTIONS
string

Additional data in the form of a JSON string that defines the context of the widget execution. For example, this could be an array containing the numeric identifier of the CRM object in the detail form where the widget handler was invoked, etc. The PLACEMENT_OPTIONS parameter, along with the PLACEMENT parameter, allows you to accurately determine for which specific placement and object the widget handler was invoked

Bitrix24 adds a URI key to PLACEMENT_OPTIONS — the path with the query string of the page from which the widget was opened. It arrives for any placement, along with the keys of that placement itself. The key is absent if the browser did not send the Referer header or if the widget was opened from a page on a different domain.

How to Parse the Call Context

PLACEMENT_OPTIONS arrives as a JSON string, not as an array: parse it on the handler side before use. The set of keys is specific to each placement and is described in the PLACEMENT_OPTIONS section of this page.

$placement = $_POST['PLACEMENT'] ?? '';
        $options = json_decode($_POST['PLACEMENT_OPTIONS'] ?? '{}', true);
        
options = json.loads(request.form.get("PLACEMENT_OPTIONS", "{}") or "{}")
        

In B24JsSDK, there is no need to parse the string: the $b24.placement.options property returns a ready object, and $b24.placement.placement returns the placement code.

What the Handler Must Return

The handler responds with a regular HTML page — Bitrix24 displays it in a frame in place of the widget. The page must allow embedding: if the application server sends the X-Frame-Options or Content-Security-Policy headers that prohibit framing, an empty area remains in place of the widget. How to fix it is described in the article Site Does Not Allow Connection.

PLACEMENT_OPTIONS

The PLACEMENT_OPTIONS value is passed as a JSON string with the call context. In addition to the universal URI key, exactly one of the two own keys arrives — USER_ID or GROUP_ID.

Required parameters are marked with *

Parameter

Description

URI
string

Address of the Bitrix24 page the widget is opened from

USER_ID
string

Identifier of the user in whose personal planner automation the widget is opened. Does not arrive in the automation of a project.

User data is returned by the user.get method

GROUP_ID
string

Identifier of the workgroup or project in whose task automation the widget is opened. Does not arrive in the automation of a personal planner.

Group data is returned by the sonet_group.get method

OPTIONS at Registration via placement.bind

This placement does not support connection parameters: the button output cannot be limited at registration.

Code Examples

How to Use Examples in Documentation

The button name is set by the TITLE parameter, and its translations by LANG_ALL.

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{
            "PLACEMENT": "TASK_ROBOT_DESIGNER_TOOLBAR",
            "HANDLER": "https://your-domain.com/widgets/task-robot-designer-handler.php",
            "TITLE": "My task automation",
            "LANG_ALL": {
              "en": {
                "TITLE": "My task automation"
              },
              "de": {
                "TITLE": "Meine Aufgabenautomatisierung"
              }
            },
            "auth": "**put_access_token_here**"
          }' \
          https://**put_your_bitrix24_address**/rest/placement.bind
        
// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        try {
          const response = await $b24.actions.v2.call.make<boolean>({
            method: 'placement.bind',
            params: {
              PLACEMENT: 'TASK_ROBOT_DESIGNER_TOOLBAR',
              HANDLER: 'https://your-domain.com/widgets/task-robot-designer-handler.php',
              TITLE: 'My task automation',
              LANG_ALL: {
                en: {
                  TITLE: 'My task automation',
                },
                de: {
                  TITLE: 'Meine Aufgabenautomatisierung',
                },
              },
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('Placement bound successfully:', result)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function bindTaskRobotDesignerToolbar() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'placement.bind',
                params: {
                  PLACEMENT: 'TASK_ROBOT_DESIGNER_TOOLBAR',
                  HANDLER: 'https://your-domain.com/widgets/task-robot-designer-handler.php',
                  TITLE: 'My task automation',
                  LANG_ALL: {
                    en: {
                      TITLE: 'My task automation',
                    },
                    de: {
                      TITLE: 'Meine Aufgabenautomatisierung',
                    },
                  },
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('Placement bound successfully:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', bindTaskRobotDesignerToolbar)
        </script>
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'placement.bind',
                    [
                        'PLACEMENT' => 'TASK_ROBOT_DESIGNER_TOOLBAR',
                        'HANDLER' => 'https://your-domain.com/widgets/task-robot-designer-handler.php',
                        'TITLE' => 'My task automation',
                        'LANG_ALL' => [
                            'en' => [
                                'TITLE' => 'My task automation',
                            ],
                            'de' => [
                                'TITLE' => 'Meine Aufgabenautomatisierung',
                            ],
                        ],
                    ]
                );
        
            $result = $response->getResponseData()->getResult();
            if ($result->error()) {
                error_log($result->error());
            } else {
                echo 'Success: ' . print_r($result->data(), true);
            }
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error binding placement: ' . $e->getMessage();
        }
        
BX24.callMethod(
            'placement.bind',
            {
                PLACEMENT: 'TASK_ROBOT_DESIGNER_TOOLBAR',
                HANDLER: 'https://your-domain.com/widgets/task-robot-designer-handler.php',
                TITLE: 'My task automation',
                LANG_ALL: {
                    en: { TITLE: 'My task automation' },
                    de: { TITLE: 'Meine Aufgabenautomatisierung' }
                }
            },
            function(result) {
                if (result.error()) {
                    console.error(result.error());
                } else {
                    console.log(result.data());
                }
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'placement.bind',
            [
                'PLACEMENT' => 'TASK_ROBOT_DESIGNER_TOOLBAR',
                'HANDLER' => 'https://your-domain.com/widgets/task-robot-designer-handler.php',
                'TITLE' => 'My task automation',
                'LANG_ALL' => [
                    'en' => [
                        'TITLE' => 'My task automation',
                    ],
                    'de' => [
                        'TITLE' => 'Meine Aufgabenautomatisierung',
                    ],
                ],
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "placement.bind", b24.Params{
        	"PLACEMENT": "TASK_ROBOT_DESIGNER_TOOLBAR",
        	"HANDLER":   "https://your-domain.com/widgets/task-robot-designer-handler.php",
        	"TITLE":     "My task automation",
        	"LANG_ALL": b24.Params{
        		"ru": b24.Params{
        			"TITLE": "My task automation",
        		},
        		"en": b24.Params{
        			"TITLE": "My task automation",
        		},
        	},
        })
        if err != nil {
        	return fmt.Errorf("placement.bind: %w", err)
        }
        
        // The response arrives as json.RawMessage — unmarshal it into the response
        // shape of the placement.bind method, see "Response Handling" on its page.
        fmt.Printf("%s\n", res.Result)
        

Common Mistakes

Mistake

Solution

placement.bind returns WRONG_AUTH_TYPE with the description Application context required

Register the placement on behalf of an application. A placement cannot be bound with a webhook

The button has appeared, but the handler receives the wrong context

Check the code: the context of a personal planner and of a project arrives with TASK_ROBOT_DESIGNER_TOOLBAR. The SONET_GROUP_ROBOT_DESIGNER_TOOLBAR placement is rendered in the same designer but passes the context of a workgroup

The handler expects both context keys and fails with an error

The keys are mutually exclusive. Check which one has arrived: USER_ID for a personal planner, GROUP_ID for a project

Other registration error codes are listed in the "Possible Error Codes" section of the placement.bind page.

Continue Learning