Create a Filter to Control Access to Subagents and Actions in the Legacy Builder
Create filters for subagents and actions to make sure that your agent can use them in a
conversation only when certain conditions are met. You can limit access based on any variable you
specify. For agents on customer channels, we recommend using filters to require authentication for
subagents and actions that perform tasks for a user.
From the Context panel, select the Filters tab, and then click
New.
Enter a name, API name, and description for your filter.
Specify whether any condition or all conditions must be met for an agent to use a subagent
or action with this filter applied.
To create a condition, specify a variable, an operator, and a value.
You can create multiple conditions. Context, conversation, and custom variables are
supported.
Save your changes.
To use your filter, apply it to one or more subagents or actions.
From the Subagents panel, click the name of the subagent that you want to modify.
To add the filter to the subagent, on the subagent's details panel, click .
To add the filter to an action in the subagent, select the This Subagent's
Actions tab, and then click the name of the action that you want to modify. On
the action’s details panel, click .
Search for and select the filter that you want to apply, and then save your changes. Your
filter is applied to the subagent or action in this agent only.
To test your filter, restart the preview conversation to apply your changes.
To view the filters applied to a subagent or action, or to add or remove a filter, from the
Subagents panel, open the details panel for that asset.
To edit or delete a filter, from the Context panel, select the Filters
tab, and then open the filter that you want to modify. You can also view all of the assets that
are currently using the filter.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.