Content triggers [Beta]

Content triggers let you build agents that run automatically when something changes in your connected data sources, no manual prompting required. Instead of you pasting a Gong transcript or Jira ticket into an agent, the system detects the event and kicks off the agent for you, passing the relevant content along as context.

Consider it as When X happens in my tools, automatically do Y.

Example use cases customers are running today:

• When a Gong call is transcribed: extract key deal information, update the Salesforce opportunity, and draft a follow-up email
• When a new Jira production or P0 ticket is created: summarize the issue, pull similar incidents and runbooks, and propose next steps
• When a Salesforce opportunity is created or moves to a key stage: summarize the deal, assess health, and recommend next actions
• Before a customer meeting: gather recent CRM, call, email, and support context into a concise meeting brief
• When a new email arrives in a monitored mailbox: draft a response

Enable content triggers

Admin can enable the content trigger feature using the following steps:

1. In Glean, navigate to Agents in the Admin console.

2. Under Setup, go to Content triggers and select one of the following options available:

   • On for everyone
   • On for some teammates
   • Off
   

You can change the access setting at any time and takes few minutes to deploy. It is recommended to start with a limited audience and expand after the team is comfortable.

Setup content trigger

Setup content trigger for Workflow mode Agents

Admins can setup content triggers using the following steps:

1. Create an agent in the Glean Agent builder using the Workflow mode.

2. Select Content as the trigger type in the zero step. This tells the agent to activate based on a data source event rather than a manual chat message.

3. Click Add trigger and select the trigger as per your requirement.

4. After selecting trigger, choose the event type and add conditions.

5. After you have added the trigger, add the Fields as per your requirement.

6. Reference the trigger content in your agent. The data from the triggering event, the transcript, ticket body, email, etc is automatically passed into the agent as content You can reference it directly in your instructions and downstream actions by use a double bracket [[Trigger input]].

7. Save the agent. After the agent is saved, it activates for any matching event.

   

Setup content trigger for Auto mode Agents

Admins can setup content triggers using the following steps:

1. Create an agent in the Glean Agent builder using the Auto mode.
2. Select Triggers.
   
3. Select Based on content updates for the field When should the agent run?.
4. Click Add trigger and select the trigger as per your requirement.
   
5. After selecting trigger, add condition.
6. Save the agent. After the agent is saved, it activates for any matching event.

Test your trigger

Before you save and deploy the agent, use sample events to verify you selected the right event type and conditions.

You can also run the agent against a sample event by clicking the play button in the event list. This helps you confirm that the trigger passes the expected input into the agent.

❗Important

Make sure the agent is saved and has no validation errors before you test or run it. If the agent is not saved, or if it still has errors, the trigger will not run.

How conditions work for new-item events

For New events, all configured conditions must be met at the time the event happens. If the record is created first and only later updated to match the conditions, the trigger does not run.

For example, if you configure a New Jira ticket created trigger with conditions such as component = mobile and owner = me, the trigger runs only if both conditions are already true when the ticket is created.

In many cases, it is better to use a meets condition event instead of a new item event. Use a meets condition event when the fields you care about may be populated or updated after the item is created.

Use trigger data in downstream steps

By default, metadata associated with the triggering event is passed into downstream steps. This includes the event details that the agent can use in instructions and actions.

Use [[trigger input]] in downstream step instructions when you want to reference the information provided by the triggering event.

If you are also passing the main body of the triggering item into the agent, keep the distinction clear and use [[trigger input]] for the triggering content itself, and use [[trigger input]] for the trigger-provided event details.

For Slack, you can configure triggers for new messages in direct messages, public channels, and private channels. You can also configure triggers for newly created public channels and private channels.

Triggers for new messages in external public channels and external private channels are not currently supported.