Conversation has message

The Teamwork Graph API is coming soon. The relationship types documented here are indicative of what will be available in the Graph via the Teamwork Graph API. Please note that relationships, their properties, and functionality may change before and during the Early Access Program.

Interested in early access? Express your interest in joining the EAP

The ConversationHasMessage relationship represents the link between an external conversation and an external message within the Teamwork Graph. It allows you to:

Retrieve messages within a specific conversation
Find which conversation a message belongs to
Traverse and analyze conversation-message relationships

Types

From Object Types	To Object Types
`External Conversation - ati:cloud:graph:conversation`	`External Message - ati:cloud:graph:message`

Cypher

Forward Query

GraphQL

1
2
query ConversationHasMessage_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on ExternalMessage {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

We recommend sending parameterized Cypher queries as below instead of embedding the parameters directly in the query string. This approach will help ensure better performance.

1
2
{
  "cypherQuery": "MATCH (conversation:GraphConversation {ari: $id})-[:conversation_has_message]->(message:GraphMessage) RETURN message",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query ConversationHasMessage_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on ExternalConversation {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

We recommend sending parameterized Cypher queries as below instead of embedding the parameters directly in the query string. This approach will help ensure better performance.

1
2
{
  "cypherQuery": "MATCH (conversation:GraphConversation)-[:conversation_has_message]->(message:GraphMessage {ari: $id}) RETURN conversation",
  "params": {
    "id": "$id"
  }
}