Overview
Creating a data structure means organizing your data into a format that is easy to use in your workflow. In Tines, this involves defining a data type, which describes the structure of the data you’re working with.
Data types in Tines are schema-less, meaning that the data doesn't have to follow a rigid structure. However, defining a clear structure helps to make the data easier to understand and work within your automation.
Tines references
Before getting started, we recommend familiarizing yourself with the surrounding functionality this article covers:
Make it happen
Core Data Types in Tines
Text: A string of characters (e.g., a name, description, etc.). This data structure is colored purple within Tines.
Integer: A whole number (e.g., 123). This data structure is colored green within Tines.
Float: A number with decimals (e.g., 12.34). This data structure is colored green within Tines.
Boolean: A true/false value. This data structure is colored blue within Tines.
Array: A list of values, which can be of any type (e.g., an array of users or event data). This data structure is identified by square brackets (“[“, “]”)
Object: A collection of key-value pairs (e.g., an object containing user information like name, email, etc.). This data structure is identified by curly brackets (“{“, “}”).
Extra Information
You might be asking, why is it important to identify these different data structure types in Tines? Here are a few reasons!:
Troubleshooting: If you misinterpret the structure, you may run into errors like trying to access an array as an object. Recognizing data structures helps in troubleshooting Tines functions and API responses effectively.
Efficient data parsing: Understanding JSON structures helps you extract and manipulate data correctly, whether it's a simple key-value pair, an array, or a deeply nested object.
Interoperability: As you’ll be working with different platform APIs in Tines, endpoint parameters may require that their value is set to a specific data structure. Familiarizing yourself with these will make it easier to work with any endpoint.
Scenario
Copy (CMD + c) the JSON block provided below and paste (CMD + v) it onto the storyboard (these are action tiles and will auto-populate!). Run them and see how the different data structures look within the Events panel.
Actions
{"standardLibVersion":"82","actionRuntimeVersion":"32","agents":[{"disabled":false,"name":"Data Types","description":null,"options":"{\"mode\":\"message_only\",\"loop\":false,\"payload\":{\"array\":[\"This is an array structure!\"],\"boolean\":true,\"float\":17.38,\"integer\":21,\"null\":null,\"object\":{\"value\":\"This is an object structure!\"},\"string\":\"This is text!\"}}","position":{"x":750,"y":1080},"type":"eventTransformation","timeSavedUnit":"minutes","timeSavedValue":0,"monitorAllEvents":false,"monitorFailures":false,"monitorNoEventsEmitted":null,"caseConfiguration":{"subStatus":null,"tags":[]},"recordType":null,"recordWriters":[],"form":null,"createdFromTemplateGuid":null,"createdFromTemplateVersion":null,"templateTags":[],"originStoryIdentifier":"cloud:0a13dfc5dbb71212cab0ad314b7fe531:f0064f807ac02bf877a6ff31d9b76916"},{"disabled":false,"name":"Real Example","description":null,"options":"{\"mode\":\"message_only\",\"loop\":false,\"payload\":{\"user\":{\"id\":42,\"email\":\"yanni@tines.io\",\"is_active\":true,\"survey_score\":96.5,\"favorite_foods\":[\"ramen\",\"burritos\"]}}}","position":{"x":915,"y":1080},"type":"eventTransformation","timeSavedUnit":"minutes","timeSavedValue":0,"monitorAllEvents":false,"monitorFailures":false,"monitorNoEventsEmitted":null,"caseConfiguration":{"subStatus":null,"tags":[]},"recordType":null,"recordWriters":[],"form":null,"createdFromTemplateGuid":null,"createdFromTemplateVersion":null,"templateTags":[],"originStoryIdentifier":"cloud:0a13dfc5dbb71212cab0ad314b7fe531:f0064f807ac02bf877a6ff31d9b76916"}],"links":[],"diagramNotes":[]}