The send email from Glean action enables Glean Agents to automatically send email notifications directly to the user.

• The action takes output generated by an agent—in any format such as text, links, tables, or bullet points—and delivers it as an email to the user who triggered or is subscribed to the agent.
• Emails are sent from Glean’s system rather than the user’s own email address.
• The email includes the agent’s name in the footer for easy identification (e.g., Sent by {AgentName} from Glean Agents).
• The action may be used in both interactive (user-triggered) and automated (subscribed) agents.

​

Usage Examples

• Automated workflow reports: An agent runs overnight to aggregate new sales opportunities, summarizes key metrics, and sends the summary via email each morning to the user.
• Task-based notifications: After processing a support call transcript, an agent analyzes key findings and emails the insights to the support agent who took the call, enabling follow-up without manual review.
• Periodic updates: A recurring agent compiles weekly meeting notes or project updates and emails them directly to the user who subscribed to the summary.
• Background research: An agent monitors web or internal data sources and, when specific criteria are met (e.g., a keyword is mentioned), emails the findings directly to the user for immediate awareness.

​

Configuration

1. In the agent builder, add “send email from Glean” as a step in your agent’s workflow.
2. Place the action as the final (or any desired) step after prior processing is complete and output is generated.
3. When the agent runs (either automatically or interactively), the action will send the output of the prior step as an email to the current agent user (the one who runs or subscribes to the agent).

​

Known Limitations

• The recipient is always the user running or subscribed to the agent; currently, specifying additional recipients or customizing the email subject is not supported. There is no preview or edit step for emails; messages are sent as generated by the preceding workflow step.
• The email is sent on the agent’s behalf by Glean and not from the user’s own account. The action uses shared Glean scio-apps to send email to the agent user.
• If an email fails to send due to technical issues, Glean relies on underlying delivery provider retry policies but does not currently have custom retry or notification mechanisms.