Type Reference

Every data type that flows between automation node ports, with the properties each object type exposes.

Overview

Automation ports are typed. A connection is only allowed when the output type is compatible with the input type, which is what lets the editor catch mistakes before a run. Object types, such as Ticket or Comment, carry their full set of properties, so a node such as Extract Properties can read any of them.

Types shown as List<T> or Field<T> are generic: they wrap another type, written in the angle brackets. A bare T is a type variable the editor infers from whatever you connect.

Primitives

Scalar values with no sub-properties.

StringNumberIntegerBooleanDateVoidAny

Ticket

PropertyType
titleString
sequence_numberString
templateTemplate
stateState
fieldsList<Ticket Field>
created_atDate
updated_atDate

User

PropertyType
idString
usernameString
nameString
emailString
imageString

State

PropertyType
idString
nameString
categoryString
colorString

Transition

PropertyType
idString
nameString
descriptionString
fromStateIdString
toStateIdString

Field<T>

PropertyType
idString
labelString
fieldTypeString
templateIdInteger

Workflow

PropertyType
idInteger
nameString

Template

PropertyType
idInteger
nameString

Iteration

PropertyType
idString
nameString
start_dateDate
end_dateDate
projectProject

Project

PropertyType
idInteger
nameString
slugString
use_caseString
current_iterationIteration
next_iterationIteration
iterationsList<Iteration>

Ticket Field

PropertyType
idInteger
labelString
fieldTypeString
valueString

Comment

PropertyType
idInteger
contentString
authorUser
createdAtDate

Follow

PropertyType
idInteger
userIdString
createdAtDate

Tag

PropertyType
iconString
colorString
labelString

List<T>

Generic container parameterised over T.

HashSet<T>

Generic container parameterised over T.

HashMap<K, V>

Generic container parameterised over K, V.

Field Value<T>

PropertyType
fieldField
valueString