Information is everywhere: code in GitHub, plans and documents in Google Drive and Microsoft SharePoint, customer and opportunity data in Salesforce, and 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:
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. We’ll continue adding new connector stories to this list as they’re published.
Explore the connector stories in the series:
1. 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.
And this is just the beginning—we have 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.
Augusto Valdez
0 comments