$last-action.name = "query_order" AND $last-action.status != SUCCESS
$last-action.name = "query_order" AND $last-action.output.orders = null
작업
트리거와 선택적 조건 평가가 발생하면 다음 작업을 실행하도록 구성할 수 있습니다.
최종 사용자에게 응답 제공: 텍스트, 조건부 응답, 맞춤 페이로드, 사전 녹음된 오디오
텍스트를 제공할 때 [pause], [pauseShort] 또는 [pause long]를 삽입하여 에이전트 음성에 일시중지를 삽입할 수 있습니다.
샘플: How can I help you today? [pause long] I can help with...
다음 LLM 작업 재정의: 도구 사용, 플레이북 호출, 플레이북 완료, 흐름 호출, 플레이북 전환, 흐름 전환
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThis page explains conditional actions, an optional feature for playbooks that allows for more control over agent behavior beyond default LLM-driven interactions.\u003c/p\u003e\n"],["\u003cp\u003eConditional actions are activated by triggers, such as lifecycle stages (like playbook start or before an LLM action) or events (like custom events or no user input).\u003c/p\u003e\n"],["\u003cp\u003eAfter a trigger, optional conditions can be evaluated using a specific syntax to determine if an action should be initiated, similar to how flow routes operate, with no conditions causing the trigger to initiate actions.\u003c/p\u003e\n"],["\u003cp\u003eConditions can reference session parameters, playbook input parameters, and details about the last or next action, including their name, input, output, and status.\u003c/p\u003e\n"],["\u003cp\u003eUpon trigger and condition evaluation, a variety of actions can be configured, including responding to the user, overriding LLM actions, modifying speech settings, and enabling features like barge-in or DTMF.\u003c/p\u003e\n"]]],[],null,["# Conditional actions\n\nBy default,\nplaybooks use LLMs to control the conversation,\ntake actions, and respond to end-users.\nIf you need more explicit control over the agent's behavior,\nyou can use\n[flows](/dialogflow/cx/docs/concept/flow)\nor *conditional actions*, which are described in this guide.\n\nConditional actions are an optional configuration for playbooks.\nYou can set conversation triggers and conditions that invoke specific actions\nlike responding with a specific message,\ncalling an external tool,\ninvoking another playbook,\nor performing any other specified action.\n\nTriggers\n--------\n\nYou can define triggers that are the first step\nin determining whether a conditional action is applicable.\nThe following describes trigger types\nand the specific triggers for each type:\n\n- **Lifecycle stage**\n - **Playbook start**: Triggered the first time a playbook is started.\n - **Before the LLM decides its next action**: Triggered every time before the LLM predicts the next action.\n - **Before the LLM executes its next action**: Triggered every time before the LLM executes an action.\n- **Event**\n - **Custom event**\n - **No input from user**\n\nConditions\n----------\n\nOnce a trigger occurs,\nthe second step is to evaluate any optionally supplied conditions.\nConditions are supplied using the same\n[condition syntax](/dialogflow/cx/docs/reference/condition)\nused by flow routes.\n\nIf no conditions are supplied,\nthe trigger alone will be used to initiate actions.\n\nYou can use the following syntax to reference parameters\nand last/next actions:\n\n- Session parameters\n - `$session.params.PARAMETER_NAME`\n- Playbook input parameters\n - `$playbook.input.INPUT_FIELD_NAME`\n- Last action (previously executed action)\n - `$last-action.name`\n - `$last-action.input.INPUT_FIELD_NAME`\n - `$last-action.output.OUTPUT_FIELD_NAME`\n - `$last-action.status`\n- Next action (LLM predicted next action)\n - `$next-action.name`\n - `$next-action.input.INPUT_FIELD_NAME`\n\nYou can also use\n[system functions](/dialogflow/cx/docs/reference/system-functions).\n\nExamples:\n\n- `$session.params.current_user = null`\n- `$last-action.name = \"query_order\"`\n- `$last-action.name = \"query_order\" AND $last-action.status != SUCCESS`\n- `$last-action.name = \"query_order\" AND $last-action.output.orders = null`\n\nActions\n-------\n\nOnce a trigger and optional condition evaluation have occurred,\nyou can configure the following actions to take place:\n\n- **Provide a response to the end-user** : text, conditional response, custom payload, and [pre-recorded audio](#pre-recorded-audio). When supplying text, you can insert `[pause]`, `[pauseShort]`, or `[pause long]` to inject pauses in agent speech. Sample: `How can I help you today? [pause long] I can help with...`.\n- **Override the next LLM action**: tool use, playbook invocation, playbook completion, flow invocation, playbook transition, flow transition.\n- **Change speech settings**: model name, no speech timeout, endpointer sensitivity, adaptation.\n- **Enable barge-in**\n- **Allow cancellation of partial response playback**\n- **Send Call Companion SMS**\n- **Enable DTMF** : see [DTMF for telephony integrations](/dialogflow/cx/docs/concept/dtmf)"]]
