Developer
News and Updates
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Object types
Relationship types
Last updated Jul 24, 2026

External conversation

The Teamwork Graph API is 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:jiraor read:graph:confluence 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 unless you have an approved path to production.

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.

Represents a conversation or discussion thread from an external communication platform. Conversations include chat threads, forum discussions, or communication channels from third-party messaging systems.

Available fields and properties

The Teamwork Graph API has the following fields and properties that you can use in your queries:

  • Object type fields are the core data fields of the object. Use these when you want to retrieve specific information about the object in your queries.
  • Cypher query properties are metadata properties used for filtering and traversing relationships between different object types in Teamwork Graph. Use Cypher query properties when you need to filter or navigate relationships between this object and other objects in your queries.

Object type fields

You can access these fields in the GraphiQL playground using the book icon in the top left, and then searching for External conversation.

FieldTypeDescription
createdAtDateTimeTimestamp when the conversation was created.
createdByUserUser who created this conversation.
descriptionStringDescription or purpose of the conversation.
displayNameStringDisplay name of the conversation as shown in the source system.
externalIdIDIdentifier of the conversation in the external system.
idID!Unique identifier for the conversation. This ID is globally unique across the entire Teamwork Graph.
isArchivedBooleanIndicates whether the conversation has been archived.
lastActiveAtDateTimeTimestamp of the last activity in the conversation.
lastUpdatedAtDateTimeTimestamp of the most recent update to the conversation.
lastUpdatedByUserUser who last updated this conversation.
memberCountIntNumber of members in the conversation.
membershipTypeStringType of membership (e.g., "PUBLIC", "PRIVATE", "DIRECT").
providerExternalProviderIdentifier of the external provider or integration that supplies this conversation.
thirdPartyIdIDAdditional identifier used by the third-party system.
topicStringTopic or subject of the conversation.
typeStringType or classification of the conversation (e.g., "CHANNEL", "DIRECT_MESSAGE", "GROUP").
urlURLDirect URL to access or view the conversation in its source system.

Fields for ExternalProvider

FieldTypeDescription
idID!Unique identifier for the external provider.
logoUrlURLURL to the provider's logo image for UI display.
nameStringDisplay name of the provider (e.g., "Google Drive", "Dropbox", "GitHub").

Available relationships

The following relationships are currently supported for External conversation:

Relationships where External conversation is the source object.

Relationship nameFrom object typeTo object type
Content entity links entityExternal conversationCompass component
Compass component link
Compass scorecard
Confluence blog post
Confluence comment
Confluence database
Confluence embed
Confluence page
Confluence space
Confluence whiteboard
External customer contact
External customer org category
External organisation
External position
External work item
External worker
External branch
External build
External calendar event
External comment
External commit
External conversation
External customer org
External dashboard
External data table
External deal
External deployment
External design
External document
External feature flag
External messages
External project
External pull request
External remote link
External repository
External Service
External space
External video
External vulnerability
Atlassian team
Atlassian team custom field value
Atlassian team type
Atlassian user
Jira board
Jira work item
Jira work item comment
Jira work item priority
Jira work item remote link
Jira work item status
Jira space
Jira sprint
Jira version
Jira worklog
Loom comment
Loom meeting
Loom meeting recurrence
Loom space
Loom video
Focus change proposal
Focus focus area
Opsgenie team
Atlassian Home comment
Atlassian goal
Atlassian goal update
Atlassian project
Atlassian project update
Atlassian Home tag
External conversation has external messageExternal conversationExternal messages
External conversation mentions Jira work itemExternal conversationJira work item
External entity is third party entityExternal conversation>> COULD NOT FIND

Rate this page: