User Attributes

1 introduction 1 introduction attributes are used to store data entered by the user during the conversation that can be later transferred or used in various use cases user attributes can also be used as variables for storing data related to a path execution for example – the email or username of a chatbot user, items ordered, quantity and delivery address for a pizza ordering bot and so on 2 how does it work 2 how does it work the following example will provide you with an in depth knowledge of its functioning for example – i have an attribute called name that will store the names of my users user a enters adam user b enters beck user c enters cenly 206,206,206 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type this information will be stored just for these users and they won’t be mixed up as we have identifiers to map them 3 methods to use attribute feature 3 methods to use attribute feature you can invoke this feature into the platform via the following methods date input nodes – request user data, form and identity node processing nodes – set attribute node display information nodes – send message with options node json and script nodes website scripts 4 system defined attributes 4 system defined attributes engati has two different sets of attributes – system defined – attributes that are automatically created by engati for capturing the data for example – facebook is a channel that provides user names of the person, hence this value is automatically pre populated in the user user name attribute a standard system attribute has a structure {{user \<attribute name>}} example attribute for full name {{user user name}} this is a system generated custom attributes – attributes created by the users for their use case system defined attributes generate values based on the channels they are deployed on z the type and name of the attribute are defined while creation note attributes that are already present in the bot are system defined and we would encourage users to not create another attribute with the same name as a system defined attribute this overrides the existing functionality of value generation and makes it a custom attribute that in turn will no longer automatically capture the values 5 viewing and using attribute values 5 viewing and using attribute values to call an attribute inside the relevant node you can use the { and a dropdown will be shown with the list of attributes to call an attribute inside the script node you can use the # and a dropdown will be shown with the list of attributes you can use apis to filter out results based on attribute name and their value by the engati api attributes and their values are stored for each user that can be accessed via the users page 6 standard attribute length 6 standard attribute length the attributes are limited in size by design the constraint is due to performance factors here are the standard limits up to 25k characters for in flow usage up to 1000 characters for also persisting this information in db for reporting and segmentation note for double byte characters, these limits may be halved in order to deal with larger data, it is a standard practice for any development to split the data or use paginated responses in case of any issues feel free to reach out to support\@engati com