Teamwork Graph is Atlassian's unified data layer that connects teamwork data from across Atlassian apps, like Jira and Confluence, as well as external tools. It enables organizations to centralize their data, break down silos, and streamline workflows. For developers, Teamwork Graph offers opportunities to contribute to and leverage this unified data model, enabling richer integrations and smarter, more contextual experiences for users.

At its core, Teamwork Graph is a common data model that represents the building blocks of teamwork: work items, documents, messages, users, groups, projects, and more. Each item—such as a Jira work item, Confluence page, or Google Drive file—is represented in Teamwork Graph as an object.
Every object belongs to a specific object type, which defines its category and the set of properties it has. When you query the Teamwork Graph API, you'll work with API object types such as Jira work item or User. When you build connectors, you'll map external data (for example, Asana tasks or GitHub issues) to connector object types like Work item. This standardization allows data from both Atlassian apps and external tools to be integrated, queried, and related in a consistent way.
Teamwork Graph connectors are available through Forge's Early Access Program (EAP).
EAPs are offered to selected users for testing and feedback purposes. We are currently working with a select group of EAP participants to get their apps production-ready and available for publishing on Marketplace.
If you are interested in joining this EAP, you can express interest through this form.
Teamwork Graph connectors bring data from external apps and tools into Teamwork Graph. Atlassian provides 100 out-of-the-box Teamwork Graph connectors that allow customers to connect popular tools to Teamwork Graph. With the Teamwork Graph connector module (EAP), you can now also build custom Teamwork Graph connectors to connect data from your app or other external tools to Teamwork Graph.
Teamwork Graph connectors work by:
Once in Teamwork Graph, this data can be used across Atlassian experiences like Rovo Search, Chat, Agents, and Atlassian Analytics. Note that currently, some experiences require additional configuration or code changes to enable data visibility.
Teamwork Graph doesn't just store data—it maps relationships between objects. For example, it can link a document to a Jira work item, or a message to a project. These relationships are what enable powerful, context-aware features like:
The Teamwork Graph API will be made available through Forge's Early Access Program (EAP).
EAPs are offered to selected users for testing and feedback purposes. These features are unsupported and are subject to change without notice.
You must only install apps that call the Teamwork Graph API in test organizations. Apps calling
the Teamwork Graph API require the read:graph:jira scope, which provides access to Teamwork Graph
data across your entire organization. While apps still respect end-user permissions, this scope may
grant access to sensitive information. For safety, only install these apps in organizations with test
data. Do not install apps using this API in organizations with production data while this feature is in EAP.
Additionally, this EAP has significant limitations. To review the full list of limitations, see Limitations and considerations.
You must be part of this EAP in order to use the Teamwork Graph API. Express interest in joining through this form.
The Teamwork Graph API lets your apps access objects and relationships in the graph, giving you a single, consistent view of data from Atlassian and connected tools. With the Teamwork Graph API, you can:
Integrating external data into Teamwork Graph gives customers a more complete and accurate picture of how their organizations work. By bringing in information and context from outside Atlassian, customers can streamline workflows, improve collaboration, and gain richer insights across teams.
This enables a range of benefits for customers, including:
While Teamwork Graph operates behind the scenes as part of the platform, users feel its impact in many ways, such as through:
| Feature | Description | Example |
|---|---|---|
| Unified search | Search for content across Atlassian and third-party tools from a single interface. | Find a Google Drive file while working in Jira or Confluence. |
| Integrated workflows | Automate and streamline processes that span multiple tools. | Automatically create Jira work items from CRM events or sync tasks between Jira and another tool. |
| Personalized recommendations | Get intelligent suggestions based on unified data and user context. | Suggest relevant documents or collaborators for a project. |
| Analytics and insights | Visualize and analyze data from multiple sources in Atlassian Analytics. | Generate cross-tool dashboards and reports. |
For your app, the Teamwork Graph API lets you tap into this unified data to power features like cross-tool dashboards, graph-aware automations, and AI experiences that understand how work and people are connected. These capabilities reduce context switching, improve efficiency, and create a more cohesive user experience. Teamwork Graph extensibility is key to this, as it allows you to build applications that become integral to delivering these richer, more connected customer experiences.
Rate this page: