Skip to main content

Types of agent triggers

In Glean Agents, a trigger is how you choose what starts an agent and what information it receives up front. Triggers define the experience for people running the agent—whether they type a message, fill in a form, or the agent runs on its own when something changes in a connected system or at a scheduled time.

Chat message trigger​

Use the chat message trigger to build a conversational agent that handles diverse requests, such as answering employee questions about HR policies.

Users can interact with the agent in the following ways:

  • Freeform messaging: Type questions directly into the chat box.
  • File attachments: Upload files to provide extra context.
  • Document tagging: Type @ to reference specific documents.
note

Glean automatically includes attached files and tagged documents with the message when sending it to the agent.

Agent context and conversation starters​

  • Session context: Every step in the agent automatically receives the current user message, along with all previous user messages and agent responses from the active chat session.
  • Conversation starters: You can configure optional conversation starters in the chat message trigger. To add dynamic inputs, use the [[placeholder]] format. When a user selects a conversation starter that contains placeholders, Glean prompts the user to enter those values before sending the message.

Automatic routing​

Administrators can configure Glean to automatically route specific user questions to a conversational agent:

  • Agent visibility: When creating a route, administrators can select only published, company-wide agents. Private or unshared agents do not appear in the selection list. For setup steps, routing conditions, and system limits, see Route requests to agents.
  • Assistant behavior: When an administrator configures auto routing for a chat message agent, Glean Assistant answers matching messages with that agent and displays the agent name on the response.
  • Agent builder previews: When you preview a chat message agent in Agent builder, the agent runs directly rather than through auto routing.

To generate an answer without the routed agent:

  1. Select Remove on the agent chip. Glean regenerates the response without the agent and stops routing follow-up messages in that chat session.
  2. Start a new chat if you want matching messages to trigger auto routing again.

Input form trigger​

Use this to create a task based agent that executes a specific workflow, for example, suggest how to resolve a support ticket. This will display a form with the input fields that the agent needs to complete the task.

  • There are 4 possible input field types:
    • Text: freeform text
    • Document: requires the user to either upload a document or enter the URL of a document that is indexed by Glean
    • Multiple choice: presents the user with a set of options to choose from
    • Date: presents the user with a date picker
  • Input fields are not automatically presented to steps in the agent. Instead, you must explicitly tag an input field using the format [[input field name]] when you want a step to have access to it.

Content trigger​

Use this to run an agent automatically when something changes in a connected tool. The changed content is passed in as [[Trigger input]].

For supported sources, events, filters, and access controls, see Content triggers.

Schedule trigger​

Use this to run an agent automatically on a recurring schedule, for example, send a weekly summary of open support tickets.

  • In auto mode, you can select On a schedule in the Agent builder or add a personal schedule to an existing agent that uses Manually run. Open the agent and select Set schedule. You can keep running it manually.
  • In workflow mode, select Input form trigger, and then select the Allow agent to run on a schedule checkbox. After you publish the agent, each user schedules and activates it from the Agent library.
  • An admin must turn on Scheduled triggers for the user in the Admin console.

For setup steps, saved inputs, and access controls, see Schedule triggers.