Glean has added 85+ new actions to its Agents and Assistant, enabling secure task execution across tools like Salesforce, Jira, GitHub, Confluence and Google Calendar. Instead of just answering questions, Glean Agents can now update records, sync documentation, and schedule follow-ups — while respecting existing permissions and admin-defined guardrails.

Enterprise teams don’t struggle because they lack information — they struggle because turning insight into execution requires constant app-switching, repetitive updates, and manual hand-offs.

Glean’s February Drop tackles that gap with 85+ new enterprise actions across tools like Salesforce, Jira, GitHub, Confluence and Google Calendar. The practical change is simple: Glean Agents can do more than summarise or recommend. They can take the next step — updating, syncing, and scheduling — without users leaving the flow of work.

Updated as of 19/02/2026: This post reflects Glean’s February Drop announcement and the corresponding Help Centre release note for “85 new actions available in Glean Assistant & Agents”.

What are “Agent Actions” in Glean?

In Glean, actions are pre-built, enterprise-grade capabilities that allow an agent to perform a task inside connected systems — for example, updating a Jira issue, creating a calendar event, or modifying a Salesforce record.

The key difference from lightweight automation is that actions are designed to:

• respect the organisation’s existing permissions model

• run with admin-defined controls

• support human-in-the-loop review where needed

What’s new: 85+ actions across core enterprise tools

Glean has expanded its action library with 85+ new actions spanning:

• Salesforce (e.g., update fields, progress opportunities)

• Jira (e.g., update issues, add comments, capture root causes)

• GitHub (e.g., create or update issues/PR-related tasks depending on configuration)

• Confluence (e.g., create or sync documentation/postmortems)

• Google Calendar (e.g., schedule follow-ups, create events)

These actions are supported in Glean Agents and Glean Assistant, and administrators enable them from the Admin console.

Why this matters for teams

Most “AI at work” value is lost in the last metre — when the answer is right, but execution still requires manual effort.

Actions close that loop. Instead of:

• reading a summary

• jumping into Jira

• updating a ticket

• then switching to Confluence to document it

…teams can ask an agent to do the work, with the right controls.

Practical examples you can use immediately

Here are realistic ways the 85+ actions can reduce admin and improve consistency.

Product and engineering

• “Update these Jira issues with the agreed priority and add a summary comment.”

• “Create a Confluence postmortem template for this incident and link the Jira epic.”

• “Based on the PR discussion, capture the decision in Confluence and assign follow-ups.”

Sales and revenue teams

• “Update the Salesforce opportunity with next steps and schedule a follow-up for Tuesday.”

• “Create a task list for this account plan, then add meeting notes to the record.”

Operations and leadership

• “Turn these meeting notes into action items and schedule a check-in with owners.”

• “Sync our project status doc and update the relevant Jira milestones.”

Rollout guidance: how to deploy actions safely

If you’re introducing agent actions, the biggest win is also the biggest risk: the agent can change systems.

A sensible rollout looks like this:

1) Start with low-risk actions

Begin with actions that are reversible and auditable:

• adding comments

• drafting documentation

• scheduling internal meetings

2) Define approval thresholds

Set a policy for what requires review:

• customer-facing changes

• financial / contractual edits

• permission or access changes

3) Use least privilege by default

Where possible, scope actions to the minimum roles and apps required.

4) Measure impact, not just usage

Track metrics like:

• time saved on updates and handovers

• reduction in duplicate documentation

• fewer missed follow-ups

• faster cycle time from decision to execution

How Generation Digital can help

If you’re exploring Glean (or expanding beyond search into agents and actions), we can help you:

• identify the highest-ROI workflows

• define governance and rollout guardrails

• enable integrations and permissions cleanly

• train teams on repeatable patterns so adoption sticks

Summary

Glean’s 85+ new Agent Actions push enterprise AI past “helpful answers” and into “helpful execution”. The organisations that benefit most will be the ones that roll it out like a capability, not a toy: start small, keep human review where it matters, and scale based on measurable workflow gains.

Next steps

• Choose one workflow to pilot (e.g., Jira updates + Confluence sync, or Salesforce updates + scheduling).

• Enable actions in the admin console for a small group.

• Define review guardrails.

• Measure outcomes and expand.

6. FAQs

Q1: What platforms are supported by the new Glean actions?
Glean’s February Drop added 85+ actions across tools including Salesforce, Jira, GitHub, Confluence and Google Calendar, with additional actions available via other integrations depending on your setup.

Q2: How do these actions enhance productivity?
They reduce context switching and manual updates by letting agents update records, sync documentation, and schedule follow-ups directly in connected tools — with permissions enforced.

Q3: Are these actions secure and scalable?
Glean positions actions as enterprise-grade, respecting existing permissions and enabling admin-defined guardrails and human-in-the-loop controls so organisations can scale safely.

Q4: Where do admins enable these actions?
According to Glean’s release notes, admins enable the new actions for their organisation from within the Admin console.

Q5: What’s the best way to start?
Pilot one low-risk workflow first (comments, drafting docs, scheduling), define approvals for high-impact changes, and measure time saved and cycle-time improvements before scaling.