Ok – let’s move this along a bit, and see if we can personalise and automate the message itself using variables.
Variables are little bits of code that will automatically insert some text into your Trigger or Action when the algorithm is triggered.
Variables start and end with two curly brackets: {{variable name}}
When the system sees the two opening curly brackets, it knows that the next part of the Trigger or Action will have to be inserted by the programme. This is done whilst the programme is running i.e. it is dynamically generated. The things within the curly brackets are called variables because they can vary every time the programme runs. When the system reaches the closing curly brackets, it knows that the sentence will continue as normal after this.
Drag and drop the variables next to what will be dynamically generated when the algorithm is triggered.
{{CurrentLocation}}
{{CurrentLocationImg}}
{{OccurredAt}}
{{NumberMissedCall}}
So let's use a variable in a real life scenario: When my phone battery gets to 1%, I’d like to automatically send my parents a map image of where I am, so they know I'm ok.
Very good! You have variables worked out!
Let's move on to 'daisy chaining' your algorithms.
Let's have a look at where you went wrong;
| You chose | Correct Answer | |
|---|---|---|
| The Trigger Channel | Battery | When my phone battery gets to 1%, I’d like to automatically send my parents a map image of where I am, so they know I'm ok. |
| The Trigger | When battery drops to 1% | When my phone battery gets to 1%, I’d like to automatically send my parents a map image of where I am, so they know I'm ok. |
| The Action Channel | SMS | When my phone battery gets to 1%, I’d like to automatically send my parents a map image of where I am, so they know I'm ok. |
| The Action | Send a text | When my phone battery gets to 1%, I’d like to automatically send my parents a map image of where I am, so they know I'm ok. |
Give it another go to get this right before we move on.