Operator Notification in MAX

Notify An Operator In MAX About A New Request

Use the same Message step with a different recipient to notify an operator:

Connect a MAX bot to the project. For a private notification, the operator must message this bot so their dialog appears in Senler. For a group notification, the bot must be able to send messages to that group, and the group dialog must be available in Senler.
In a For dialogs automation, place Message after the Update table row step successfully runs in Append new row mode. The message will then refer to a saved request.
Set Channel types to MAX and Where to send to Selected dialog. Select the required MAX dialog with the operator or group. Current dialog would notify the client who started the run.
Keep Whose data to use in variables set to Run lead and dialog. Use the variable picker to insert the client's name and saved request details. Recipient data in this case belongs to the operator.
If the operator needs the client's contact, attach a lead contact and select Current process lead.
Check the recipient and message before publishing. A test send also delivers a real message to the selected operator.

The MAX token is stored in channel settings. This send does not need an HTTP request step, a MAX API URL, or a token in the workflow text. If the channel or operator dialog is not connected yet, complete the connection and recipient selection first.

When an Agent Saves the Request

If an agent fills the table, adding a row does not itself start this automation. For a workflow with one pending request, the agent can add the lead to a separate segment after a confirmed write and start the workflow on segment entry. Remove this marker only after the notification is sent successfully. While the lead is already in the segment, adding it again is not a new subscription: the segment does not replace a separate event for each row when multiple requests are pending at once.

Configure the notification recipient and variable source in the Message step.