Agent Result

First configure the Run agent step. It prepares a result for the current dialog but does not send a message to the customer itself.

Save The Response To Variables

In Agent response, choose where each result should be stored. The picker shows the scope and name, for example, Run · agent_response_text:

• Run keeps the result only in this run and makes it available as {{run.name}};
• Lead stores the result for the current lead and keeps it available to later runs as {{lead.name}};
• Dialog stores it for the current conversation as {{dialog.name}};
• Project makes it a shared project value available as {{project.name}}.

Then choose which parts to store:

• Response text: the prepared text;
• Response attachments: files prepared by the agent;
• Response button block: buttons for the next Message step;
• Full response (JSON): the text, attachments, buttons, and event identifier in one object.

The list shows only compatible variables: a string for text, an array for attachments and buttons, and an object or JSON variable for the full response. If a suitable lead, dialog, or project variable does not exist, create it from the picker; permission to create that type of variable is required.

Keep only the results that later steps need, and do not select the same variable for two results in one step.

Connect the Response output to the next step. It is used when the agent has not selected an additional output. The automation continues after the agent finishes and the selected variables are populated.

If the agent schedules a delayed message without preparing a response now, the step keeps waiting. When the timer fires, the agent resumes within the same run; once the result is ready, the automation stores the variables and continues. The timer itself does not send the result to the client: you still need a Message step.

Send The Result To The Lead

In most workflows, a Message step follows Run agent:

1. Insert the reply-text variable into the message, for example {{run.agent_response_text}}.
2. If needed, select Response attachments as the attachment source.
3. Under Add button, create a Dynamic button block and select the Response button block variable.
4. Connect the message's regular output to the next workflow branch.

The attachment source, dynamic-button, and clicked-button fields support Run, Lead, Dialog, and Project variables. Lead and Dialog are unavailable in a Background automation. Use the same scope for a result and the next source field so the value remains available. The pencil in a variable field lets you enter a nested path.

If the agent returned buttons, configure continuation after a click.