The action adds an entry to the absence chart. The action parameters are the same as when an entry is added to the absence chart manually.

• User - specify the user for whom the event will be entered in the absence chart.

• Event name - the name of the event in the absence chart.

• Event description - detailed description of the event for the absence chart.

• Start date - date and time when the event starts.

• End date - the date and time when the event ends.

• Absence type - select the type of absence from the list.

• State - specify the user's state for the period of absence. It will be displayed in the user's profile.

• Completion status - specify the user's state when the absence is over.

When a user launches a workflow, this action will add an entry to the absence chart.

Also, the absence will be displayed in the user's profile.

The action sends a new message to Feed.

Sender - select a user that will be displayed as the sender of the message.

Recipients - specify users, groups of users, or departments that will receive the message to Feed.

Message title - specify the message title.

Message text - specify the message text. You can use BBCode tags.

Target site - select a site to which Feed the message will be sent.

When a user launches a workflow, this action will add a new post to Feed.

The action adds an event to a calendar.

• Calendar type (optional) - specify the calendar type, in which the event will be created. To create an event in a user's personal calendar, you do not need to specify the user type. If the field is empty, the event will be created exactly in this calendar.

• Calendar owner ID (optional) - specify the calendar owner ID. If an event is created in the group calendar, its identifier is displayed.

• Calendar section ID (optional) - get the value of this field from the database, from the page source code, or the AJAX request analysis. Therefore, a developer should fill this field.

• User- specify the user, for whom the calendar event will be created.

For example, to add an event to a workgroup calendar, complete the parameters as follows:

• Calendar type (optional) - group
• Calendar owner ID (optional) - 50

You can find the values for the Calendar type (optional) and Calendar owner ID (optional) parameters in the workgroup address link.

When a user launches a workflow, this action will add a new event to the specified workgroup calendar.

The action creates a task. Most action parameters are the same as when you create a task manually. Let's consider an example of a business process in CRM to see some particularities.

• Pause process while task is running - if this option is selected, the workflow will be stopped until the created task gets to the Finished status.

  

• Bind to current CRM entity - the task will be linked to the CRM entity, for which a workflow is launched. For example, if you run a business process in a deal, the task will be linked to the deal.

• CRM Items - the parameter allows you to link the task to other CRM entities. You can select a specific CRM item from the list or substitute it through the Insert Value form.

  

  To bind entities through the form, you should use the following syntax:

• Contacts:="C_"&{{ID}}
• Deals:="D_"&{{ID}}
• Leads:="L_"&{{ID}}
• Companies:="CO_"&{{ID}}
If you have a field with Bind To CRM items type, you should also use the following prefixes to bind entities specified in this field: ="C_"&{{ID}}, ="D_"&{{ID}}, ="L_"&{{ID}}, ="CO_"&{{ID}}.

• Load files - the parameter allows you to attach files to the task.

  

When a user launches a workflow, this action will create a new task with all the specified parameters.

The action sends an email message to an employee from the sender indicated in the action settings.

Message Type - indicates how the message will be sent: as a text or using HTML.

Encoding - sets the encoding of the message to be sent.

Message send mode - sets the way of sending the message:

• Direct sending - the message will be sent immediately.

  It is a preferable option for companies that do not send a large number of emails.

• Send using Mail Subsystem - the message will be sent using the embedded mail system. The sending can be postponed.

  If you often send emails and bulk email campaigns, this option will be more suitable for you.

Message template website - indicates the message template site to send the message through the embedded mail system. Different sites can have different templates of mail messages.

Attachments - you can attach files to a message, or select a drive file (Bitrix24 Drive).

Email address separator - select a symbol that will be used for separating email addresses if you're going to send messages to several emails.

When a user launches a workflow, this action will send an email to the selected employees.

The action sends a notification message to a selected user. If he/she is not online, the user will get a notification via email.

• Sender - specify the author of the message.

• Recipient - add a specific user or a group of users.

• Message Text - enter the text of the message that the recipient will see.

The action performs pre-recorded or text-based robocalls to a specified number.

• Destination number - enter a phone number or the string field of the element where you specify a phone number.

• Wait for result - indicate if you want to stop the business process execution before the voice bot finishes calling customers.

This action sends the supervisor a notification message about overdue tasks and violations.

• Message text - specify the text of the notification.

• Send to supervisor - decide whether to select the direct employee's supervisor according to your company structure or insert another value.

• Additional recipients - specify other users you need to notify. If you select no in the previous parameter, you should add notification recipients there.

When a user launches a workflow, this action will send a notification to the responsible person's supervisor.

This action sends a message to the open channel that the customer last contacted.

• Message text - specify the text of the message.

• Hidden message (whisper mode) - enable this option if you want only the employees who are present in the chat with the client to see the messages.

• Attachment type - select the attachment type: Element Files or Drive.

• Attachments - you can attach files to a message via Insert Value form (if you select Element Files), or from Bitrix24.Drive (if you select Drive).

This action changes the text of the element status. It makes it easier to monitor the element state in the general list of business processes.

The current status can be viewed in the detailed view of the element for which a business process is launched.

The action sends notifications to a user. If the user is not authorized on the site, the message will be additionally sent by email.

• Notification text - specify the text of the notification.

  You can use BBCode tags ([b], [i], [s], [u], [url]).

• Notification text for email/jabber - set the message text for email notification to be sent if the user is not authorized on the site. If you leave this field empty, the "Notification text" will be used.

• Notification type - you can select if the notification will be displayed as a notification from the other user, or it'll be displayed as a system notification.