Information is everywhere: code in GitHub, plans and documents in Google Drive, Microsoft SharePoint, and OneDrive, customer and opportunity data in Salesforce, and conversations and decisions in Microsoft Teams and Slack—alongside teamwork spread across Jira, Confluence, and other tools.
The challenge isn’t a lack of information—it’s finding the right context when you need it.
That’s where Teamwork Graph connectors come in. By connecting the tools teams already use, organizations can bring relevant third-party context into Atlassian and make it available across Rovo Search, Chat, Agents, and in external AI agents like Claude.
With connected context, teams can:
- Find information across tools without switching between tabs
- Understand work in context, rather than looking at isolated records or documents
- Prepare faster for meetings, reviews, launches, and customer conversations
- Connect plans, decisions, code, customer data, and delivery work
- Use Rovo to synthesize information and support repeatable workflows
- Move from finding information to taking action—with the right permissions and controls in place
Because connected context provides AI with more complete information and less fragmentation, it can help Rovo and external AI agents use tokens more efficiently and produce higher-quality outcomes.
To explore these possibilities, we’re publishing a series of blog posts highlighting the value of individual Teamwork Graph connectors and the ways they can help teams work with more context. The series now covers GitHub, Google Drive, SharePoint and OneDrive, Salesforce, Microsoft Teams, and Slack, as well as how admins can set up and govern connectors. We’ll continue adding new connector stories to this list as they’re published.
Explore the connector stories in the series:
- GitHub
Bring GitHub context into Rovo with the Teamwork Graph connector for GitHub
Learn how connecting GitHub can help software teams understand progress, prioritize reviews, connect implementation work to Jira plans, and get a clearer picture of what has shipped.
👉 Bring GitHub context into Rovo with the Teamwork Graph connector for GitHub
2. Google Drive, SharePoint, and OneDrive
Turn knowledge in Google Drive and Microsoft SharePoint into connected context
Explore how teams can use connected documents alongside Jira, Confluence, and other Atlassian context to find information, prepare updates, understand decisions, and move work forward faster.
👉 Turn knowledge in Google Drive and Microsoft SharePoint into connected context - Inside Atlassian
3. Salesforce
Connect Salesforce to the Teamwork Graph to unlock customer context for your teams and agents
See how connecting Salesforce can help sales, customer success, marketing, and support teams bring account, opportunity, contact, case, and campaign context together with the work happening across Atlassian.
👉 Connect Salesforce to the Teamwork Graph to unlock customer context for your teams and agents - Inside Atlassian
4. Microsoft Teams
Put your conversations to work with the Teamwork Graph connector for Microsoft Teams
Discover how connecting Microsoft Teams enables you to search across channels, chat history, and meeting transcripts, catch up quickly on key decisions, and turn conversation context into action alongside Jira and Confluence.
👉 Put your conversations to work with the Teamwork Graph connector for Microsoft Teams - Inside Atlassian
5. Slack
Turn Slack conversations into connected context with Teamwork Graph
Learn how connecting Slack helps teams find the decisions behind their plans and monitor launch risks with custom Rovo Agents. It also covers turning Slack threads into Jira work and coordinating incident response, all while Slack knowledge stays in Slack and existing permissions still apply.
👉 Turn Slack conversations into connected context with Teamwork Graph - Inside Atlassian
6. Connector setup and governance for admins
Say yes to AI context without losing control: a new way to set up and govern connectors in Atlassian Administration
Learn how admins can review connector prerequisites and trust information, save setup drafts, manage connectors from one place, set content and authorized-domain controls, and respond quickly with organization-wide controls for included third-party tools.
👉 Say yes to AI context without losing control: a new way to set up and govern connectors in Atlassian Administration - Inside Atlassian
And this is just the beginning—more connector stories coming soon.
Which connector would you like to learn more about? Share your questions, use cases, or experiences with connected context in the comments.
Note: Connector availability, supported content, and administrative controls may vary by connector and organization configuration.
