• Expression Syntax

  All expressions begin with an "@" symbol and an open parenthesis, e.g. @(now() or @(timefromparts() Once entered, @( will trigger a completion dialogue that lists and explains each function: Simple Syntax This is used to embed single values, e.g. Hi @contact, you entered @results.age for age. Is this correct?  An expression can also be a function call, e.g.Some readers

• Function Reference

  You can use expressions in your flows to customize messages and make more complex splits. See our detailed guide on Expressions here and see more about expression syntax here. If you have any questions, send us a message via the support widget in the bottom right corner.Few readers

• Date & Time Arithmetic

  Use this guide to write date & time arithmetic functions. For example, To add or subtract seconds, minutes, hours, days, months or years to a given date, use @datetimeadd: @(datetimeadd("2017-01-15", 5, "D"))  adds 5 days@(datetimeadd(fields.dob, -3, "M")) subtracts 3 months To create a datetime from a known datetime and a separate hour, e.g. Your next appointment is at @(replacetime(contact.createdon, time("15:00”)))  To change the time of datetime value, use the *Few readers

• Logical Comparisons

  A logical comparison is an expression which evaluates to TRUE or FALSE. These may use the equals (=), not-equals (!=), greater-than (>), greater-than-or-equal to (>=), less-than (<) and less-than-or-equal to (<=) operators, e.g. @(contact.age 18) Note that when comparing text values, the equals ( = ) and not-equals ( != ) operators are case-insensitive.Few readers

• Limiting the Number of Incorrect Responses to a Question

  You may want to set a limit to the number of times a contact can respond to a specific question in your flow, such as with a quiz or survey. You can do this by using the @node.visitcount expression within a Split by Expression action. In the example below, we've created a very simple quiz. We want the contact to have limited opportunities to answer the question, so we will place the @node.visitcount expression on a 'Split by Expression' node to limit the number of guesses. (https:Few readers