Team'26 Recap Serie - DAY #2: The Incredible Scale of the Teamwork Graph

[#1]

Hi Community! 👋

Did you catch the sessions and keynotes at Team ’26 in Anaheim? If you missed it or just want a refresher, I'me breaking down the biggest announcements over the next few days.

This is the second entry of a day-by-day serie of forum posts about key agenda topics and announcements from Team'26.

Previous article: Team'26 Recap Serie - DAY #1: The Vision — Turning Organizations from "AI Novices" to "AI Natives" 

---

Hey everyone! Welcome back to our daily recap series.

Yesterday we touched on the Teamwork Graph. Today, let's look at the sheer scale of what this engine is handling right now and the massive adoption numbers shared on stage.

📈 The Numbers Don't Lie

Atlassian shared some staggering data on how rapidly organizations are shifting toward agentic automation:

• 150B+ Connections currently live within the Teamwork Graph.
• 7X Increase in agentic automations in just the last 6 months alone.
• 14M+ Rovo-Assisted Actions executed just within the last month.

🌐 Beyond the Atlassian Ecosystem

The Teamwork Graph isn't a closed garden. It actively pulls context from across your entire tech stack, organized into clear pillars:

1. Collaboration Apps: Microsoft 365, Google Drive, Notion, Box, Dropbox, Confluence Data Center.
2. Communication Apps: Slack, Teams, Outlook, Gmail, Salesforce, Zendesk.
3. Development Apps: GitHub, Azure DevOps, GitLab, Jira Data Center.
4. Project Management Apps: Airtable, Asana, Smartsheet, Monday, Workday, ServiceNow.

🛠️ The base of an opened platform

One of the most significant announcements was that Atlassian is opening its platform to the world; through the Teamwork Graph, communication flows in both directions. This communication is enabled by the availability of MCP servers.

The Teamwork Graph forms the foundation of the entire platform. It therefore allows Atlassian’s native tools to be integrated with external agents and tools.

This image shows all the tools grouped into what Atlassian calls Collections, with the following layers:

• Teamwork Graph at the base
• AI Agents
• Atlassian tools
• Connectors to external tools

💬 Community Discussion: Seeing a 7x leap in agentic automation in half a year is wild. What’s the first non-Atlassian app you’d want Rovo to deeply analyze via the Teamwork Graph?