Skip to main content
Skip table of contents

Manipulate your variables with formatters

Last updated: 30 January 2024

Variables are at the core of your platform. Within variables, you may store values captured through conversations, integrations, third-party applications, or even built-in data.

A deep understanding of variables will unlock more of our powerful features. Make sure you get the basics before digging further into this document:

In this document, we dig further into data manipulation within variables. Beyond just storing a value (e.g. a name captured from a user or a date), our variables allow you to modify said value on the fly.

There are broadly two ways of manipulating your variables:

  • Built-in formatters

  • In-line formatters

Built-in formatters

Built-in formatters are, as their name implies, built into the platform. They are common variable manipulation use cases, so common in fact we decided to create a simple interface to make them easier to use.

Everywhere you can use variables, you have a choice to use formatters to transform a value hidden inside a variable from one format to another.

Below, we dive into each formatter and illustrate them with use cases.

Date formatter

The date formatter allows you to convert any supported date-time format into a format of your choice.

What is the use case?

Imagine you are creating a chatbot capable of booking meetings using our date picker. Our date picker uses the following date format: dd-mm-yyyy.

This is all well and good. But, if you need to send this date to an external software (a CRM, for example), they might require a yyyy-mm-dd date format.

This is where the date formatter comes in.

As you enter your variable inside the integration, use the formatter to convert the original format (dd-mm-yyyy) into the new one.

The date formatter supports the following date-time parameter strings:

String

Description

Example

Days

d

Day of the month with leading zeros

01 to 31

D

Three letter name of the day.

MonWedSun

j

Day of the month without leading zeros.

1 to 31

l (lowercase 'L')

Complete name of the day.

Sunday through Saturday

N

Numeric representation of the day of the week, starting at 1 for Monday.

1 for Monday, 3 for Wednesday, etc.

S

English ordinal suffix for the day of the month, two characters.

stndrd or th. Use in combination with j.

w

Numeric representation of the day of the week, starting a 0 for Sunday.

0 (for Sunday) through 6 (for Saturday)

z

The day of the year (starting from 0).

0 through 365

Week

W

Number of the week in the year (weeks starting on Monday).

Example: 42 for the 42nd week in the year.

Month

F

Complete name of the month.

January through December

m

Numeric representation of a month, two characters.

01 through 12

M

Three letter shortcut for the month of the year.

Jan through Dec

n

Numeric representation of a month, without leading zeros.

1 through 12

t

Number of days in the given month.

28 through 31

Year

L

Boolean showing whether it is a leap year.

1 if it is a leap year, 0 otherwise.

o

Week-numbering year. This has the same value as Y, except that if the ISO week number (W) belongs to the previous or next year, that year is used instead.

Examples: 1999 or 2003

Y

Numeric representation of a year, four digits.

Examples: 1999 or 2003

y

A two digit representation of a year.

Examples: 99 or 03

Time

a

Lowercase am or pm.

am or pm

A

Uppercase AM or PM.

AM or PM

B

Swatch Internet time

000 through 999

g

12-hour format of an hour without leading zeros.

1 through 12

G

24-hour format of an hour without leading zeros.

0 through 23

h

12-hour format of an hour with leading zeros.

01 through 12

H

24-hour format of an hour with leading zeros.

00 through 23

i

Minutes with leading zeros.

00 to 59

s

Seconds with leading zeros.

00 through 59

u

Microseconds.

Example: 654321

v

Milliseconds.

Example: 654

Timezone

e

Timezone name or identifier.

Examples: UTCGMTAtlantic/Azores

I (capital i)

Boolean showing whether or not the date is in daylight saving time.

1 if Daylight Saving Time, 0 otherwise.

O

Difference to Greenwich time (GMT) without colon between hours and minutes.

Example: +0200

P

Difference to Greenwich time (GMT) with colon between hours and minutes.

Example: +02:00

p

The same as P, but returns Z instead of +00:00

Example: +02:00

T

Timezone abbreviation.

Examples: ESTMDT ...

Z

Timezone offset in seconds.

-43200 through 50400

Full Date/Time

c

ISO 8601 date

2004-02-12T15:19:21+00:00

r

Date formatted using RFC 2822.

Example: Thu, 21 Dec 2000 16:01:07 +0200

U

Seconds since the Unix Epoch (January 1 1970 00:00:00 GMT).

Escape formatter

The escape formatter allows you to replace HTML elements into their unicode counterparts. To escape a variable, simply type |escape after the variable name.

What is the use case?

Imagine you need to send a value to a third-party software but:

  1. The value is likely to contain HTML elements such as <h3> or <p>

  2. The third-party software might not recognise those elements and strip them out.

You can apply the escape formatter to your variable so that <h3>hello</h3> becomes &lt;h3&gt;hello&lt;/h3&gt;.

Explode to JSON

The explode to JSON formatter allows you to convert a simple string of text into a JSON array. This may be explicitly required for some integrations.

What is the use case?

Imagine you are trying to send the following message from your chatbot to an external piece of software which requires it in JSON: one,two,three

Your API expects a JSON array, such as ["one","two","three"].

You can use this formatter to do exactly that: {{message.message|explode_to_json_array}}

Extract value formatter

The extract value formatter allows you to extract a value appended to a postback.

What is the use case?

Imagine your business sells five different services, such as gardening services, cleaning services, and so on. You are creating a chatbot that would allow users to book your services. This chatbot contains:

  • Five FAQs, one for each service.

  • One conversation, to capture the user’s personal details.

To go from an FAQ to the conversation, you cleverly use an action message and a postback such as enquire_services. While this works perfectly, it would be quite cool to slightly modify the copy of the very first message inside the enquiry conversation to reflect which service the user was asking about originally.

With the value extract formatter, this is now possible. 

Simple append the postback on each FAQ with from(cleaning services)

Then, inside your conversation’s first message, attach a variable {{message extract=from}} to resurface the value inside from().

Number formatter

The number formatter allows you to format a number’s decimals and decimal/thousand operators.

What is the use case?

Imaging you are capturing the budget of a potential customer through your lead generation chatbot. You offer them free rein to write their budget in any format they want, but you really prefer to display it with two decimal points.

This number formatter allows you to do just that: {{message.message|number_format(2)}}.

You can also control the operators between the thousands and the decimal.

Here are examples using 9121828 as a starting number:

Format

Variable

Output

Represent thousands as . and decimals as , and two decimals.

{{custom.get.random_number|number_format(2, '.', ',')}}

9.121.828,00

Represent thousands as spaces and decimals as ., and two decimals.

{{custom.get.random_number|number_format(2, ' ', '.')}}

9 121 828.00

Represent thousands as , and no decimals.

{{custom.get.random_number|number_format(0, ',', ',')}}

9,121,828

Trying to apply a formatter to a number output from a mathematical equation between variables (see below)? Make sure you wrap the entire math equation in brackets before the formatter. For example: {{ ( custom.get.number_1 / custom.get.number_2 ) |number_format(2) }}.

Regex formatter

The extract value with regex formatter works like the extract value formatter, except it will grab the first item that matches the inputted regex.

The platform uses PHP Regex which is slightly different to ‘normal’ Regex.

What is the use cases?

Here are a few common use cases.

  • Truncate the value inside a variable to its first 100 characters: {{variable-name|regex("/^(.{0,100})/")}}.

  • Truncate the value inside a variable to its last 5 characters: {{variable-name|regex("/.{5}$/")}}.

  • Truncate the value inside a variable after a specific set of characters. For example, if an insurance policy ID always starts with ABC then a string of characters and you want to only extra the characters, you would write: {{variable-name|regex("/ABC(.*)/")}}.

  • Truncate the value inside a variable as soon as it encounters a specific character. For example, if you want to extract alex from alex@google.com, you would write: {{variable-name|regex("/^(.?)@.$/")}}.

  • Extract the value contained between two specific characters inside a variable. For example, if you want to extract the value between £ and @, you would write: {{variable-name|regex("/£(.*?)@/")}}.

  • Remove the . at the end of a variable: {{variable-name|regex("/^(.*?)(\\.|$)/")}}. Ideal for capturing variables in VOIP conversations.

For more help on PHP Regex, read the W3 guide.

Query parameters

The URL parameters formatter allows to extract a value behind the parameter of a URL.

What is the use case?

Imagine your chatbot lives on a page of your website. To get to that page, users need to log into your web portal. Once logged in, they are redirected to a page where they can interact with your chatbot. This page URL has the following format:

https://my-website.com/welcome?token=lwpl2aow12019kda

What you would really like to do is verify that every single user talking to your chatbot is actually logged in. The URL parameter formatter allows you to do that by extracting the value behind token=. Once extracted, this token can be used in an integration to verify the user is, indeed, logged in.

Convert variable type formatter

The convert variable type formatter allows you to convert data format into another.

What is the use case?

Imagine you are setting up an integration. This integration allows you to capture data inside your chatbot and send it to an external software.

Alas, the data captured inside your platform adheres to a number format and the external software only accepts JSON format. Here comes the convert variable type formatter!

Use this formatter to change number, float, or JSON formats for another.

Unique

The unique formatter allows you to only return the unique values out of an array.

What is the use case?

Imagine you are creating a fuzzy composer which you’d like to populate with the values of a spreadsheet. Your spreadsheet has hundreds of duplicates. If you were to merely import this spreadsheet and create your composer, it would contain all these duplicates.

With Unique, you can strip out all the duplicates and only return unique values.

Here’s a tutorial on this exact use case.

In-line formatters

On top of the built-in formatters, you can also manipulate data by manually adding ‘code’ to the variables. Knowing some of the key in-line formatters will help you work quicker.

In-line formatters are often used to manipulate multiple variables at once.

There is no interface for in-line formatters, you will need to remember them (or refer back to this doc!).

There is no interface to format variables in-line. This means you will need to first add your basic variable then manually add your in-line formatters to it.

Math

Performing calculations on one or multiple variables is very common. Some examples include:

  • Creating an interest rate calculator

  • Adding up the cost of several items

  • Applying a discount

You can in-line mathematical operations inside variables like so: {{ variable_name + 20}}.

In this simple example, the variable would return the original value of {{ variable_name }} plus 20.

It is good practice to add brackets around your mathematical equations. For example, assuming number 1 is 3 and number 2 is 5:

{{ ( custom.get.number_1 / custom.get.number_2 ) }} = 8

{{ (custom.get.number_1 + custom.get.number_2) / 2 }} = 4

{{ custom.get.number_1 + (custom.get.number_2 / 2) }} = 5.5

And so on. Brackets matter, particularly if you are using formatters.

The following operators are available:

Operators

Breakdown

+

Adds two numbers together.

-

Subtracts the second number from the first one.

/

Divides two numbers.

%

Calculates the remainder of an integer division. For example 11 % 7 is 4.

//

Divides two numbers and returns the floored integer result. For example 20 // 7 is 2.

*

Multiplies two numbers together.

**

Raises the first number to the power of the second. For example 2 ** 3 would be 8.

( )

Groups different parts of an equation together. For example, (2 * 3) + 4 would be 10 but 2 * (3 + 4) would be 14.

On top of the simple example above, you may also in-line mathematical operations between one or multiple variables like so:

{{ variable_one * variable_two }}

Concatenate values

Using the operator ~, you can concatenate one or several values into one.

For example, imagine you are capturing a user’s first name and last name in two variables, {{ custom.get.firstname }} and {{ custom.get.lastname }}.

You can return their entire name using the following in-line formatter:

{{ custom.get.firstname ~ ' ' ~ custom.get.lastname }}.

The ' ' in the middle provides a space between both values.

FAQs

Can I combine in-line and built-in formatters?

Of course! Here’s a simple example of in-lined math with a Number formatter.

{{ ((custom.get.number * 3) / 18)|number_format(2)}}

In this example, if custom.get.number was 23 the returning value would be 3.83.

Can I use formatters in dynamic templates?

Indeed you can. Here’s an example:

CODE
{% if address.number ~ ' ' ~ address.address1 ~ address.address2 == custom.get.user_address_line_1 ~ custom.get.user_address_line_2 %}

In this example, we write an if statement where we compare the concatenated value of address.number, address.address1, and address.address2 with the concatenated value of custom.get.user_address_line_1 and custom.get.user_address_line_2.

(Advanced tip: you’ll notice the first three variables do not contain custom.get. That is because they are third-party values pulled from an API call. That’s right; formatters also work on third-party variables!).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.