Developer
Documentation
Resources
Get Support
Sign in
Developer
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Developer
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Last updated Jul 16, 2025

Connecting to Teamwork Graph

What is Teamwork Graph?

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.

This transformation is made possible by the foundation of Atlassian’s platform: Teamwork Graph. Teamwork Graph is a powerful data layer that connects people, work, and knowledge across all Atlassian experiences. For the first time, apps will be able to both contribute to and leverage this unified data model, enabling richer integrations and smarter, more contextual experiences for users.

How does Teamwork Graph work?

Unified data model

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. For example, Jira, Asana, and GitHub all have different objects that represent work. Jira has Work items, Asana has Tasks, and GitHub has Issues. In Teamwork Graph, these are grouped under the object type Work item. This standardization allows data from different tools to be integrated, queried, and related in a consistent way.

Adding data to Teamwork Graph (EAP)

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:

  • Extracting data from the source system (e.g. Google Drive, Slack, a custom app).
  • Mapping that data to Teamwork Graph’s object types and schemas.
  • Pushing the data into the graph via bulk APIs, including objects, users, groups, and their relationships.
  • Sending permissions and access control lists (ACLs) for each object, so data is secure and only visible to the right users.

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.

Relationships and context

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:

  • Unified search across all tools
  • Personalized recommendations
  • Cross-tool automation and analytics

Accessing data in Teamwork Graph Coming soon

Today, developers can add data to Teamwork Graph via connectors. Soon, you’ll also be able to access data from the Graph in your apps. This will allow you to:

  • Query the graph for objects, relationships, and insights using an API.
  • Build apps that leverage unified data for analytics, reporting, workflow automation, and AI-powered features

This two-sided model—adding data to the Graph and accessing data in the Graph—makes Teamwork Graph a true platform for extensibility.

What value does Teamwork Graph provide?

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:

  • Reduced tooling complexity: Centralize workflows and minimize the need to switch between applications.
  • Improved productivity: Unified access to data and automated workflows save time and reduce friction.
  • Enhanced collaboration: Teams can easily find and share information, fostering better communication and alignment.
  • Smarter insights: Unified analytics and AI-driven recommendations help teams make informed, data-driven decisions.
  • Scalability: Easily integrate new tools and data sources as organizational needs evolve.

While Teamwork Graph operates behind the scenes as part of the platform, users feel its impact in many ways, such as through:

FeatureDescriptionExample
Unified searchSearch for content across Atlassian and third-party tools from a single interface.Find a Google Drive file while working in Jira or Confluence.
Integrated workflowsAutomate and streamline processes that span multiple tools.Automatically create Jira work items from CRM events or sync tasks between Jira and another tool.
Personalized recommendationsGet intelligent suggestions based on unified data and user context.Suggest relevant documents or collaborators for a project.
Analytics and insightsVisualize and analyze data from multiple sources in Atlassian Analytics.Generate cross-tool dashboards and reports.

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.

What’s possible

Connecting to Teamwork Graph provides you with a unique opportunity to build smarter, more integrated applications within the Atlassian ecosystem. Some examples of use cases include:

Adding data to Teamwork Graph

  • Unify data across tools: Build connectors that ingest data from third-party SaaS tools (like Google Drive, Slack, Salesforce, Workday, GitHub, etc.) or internal systems into Teamwork Graph.

  • Enhance existing apps: Add a Teamwork Graph connector to your existing app so that its data becomes discoverable and actionable across Atlassian experiences, such as Chat and Search.

  • Power analytics, reporting, and AI: Ingest data into Teamwork Graph to enable advanced analytics, reporting, and AI-driven insights.

Accessing data in Teamwork Graph Coming soon

  • Power your app with unified data: Fuel your app’s features with comprehensive data from across Atlassian and connected third-party tools, enabling richer, more integrated user experiences.
  • Enable smarter features: Leverage relationship and activity data to deliver smart recommendations, personalized dashboards, or context-aware features.
  • Detect patterns and insights: Traverse the graph to uncover dependencies, blockers, or collaboration patterns—powering advanced analytics and workflow automation.
  • Simplify integration: Access unified cross-app and cross-tool data through a single GraphQL endpoint, eliminating the need to stitch together multiple Atlassian app-specific APIs and accelerating development.

Get started

To get started extending Teamwork Graph, check out the following resources:

Forge modules

Reference documentation

Example apps and tutorials

Rate this page: