¶ Scenario actions
Whenever a scenario is triggered, all actions will be performed automatically. Each scenario can be configured with one or multiple actions. All actions will be performed sequentially when the scenario is triggered. When an action supports custom texts, dynamic information can be added based on the event that triggers the scenario. Dynamic information such as device name, date, time, alarm type, geofence name, beacon name and much more.
¶ Show at alerts page
Shows the event information as an alert. You can provide a title and a message that is displayed in the alerts page.
¶ Text message on device
Sends an on-screen message to the selected device(s) and/or the device(s) in the selected team(s) and/or geofence(s). Message delivery parameters are available for certain devices. Like tone , volume, vibration, or to automatically remove the message after a given delay.
Some devices support acknowledgements and when the do, it is also possible to select a follow-up scenario for when the message is not acknowledged. To create such a scenario, please refer to the Message not acknowledged scenario trigger.
¶ Voice message
The platform makes a phone call to the configured recipients. The voice message will sound in the configured language.
You are able to select multiple recipients. You are able to select the phone number of the alerting app user. This is convenient, for example, when a text message is not acknowledged and you wish to contact this person nevertheless.
The “wait for possible new location” checkbox is explained here.
¶ SMS message
Sends an SMS message to the configured recipients.
The URL will be shortened with the cbly.in domain.
The “wait for possible new location” checkbox is explained here.
¶ Start tracking
Starts tracking the device that triggered this scenario as per configuration in this action.
¶ Call webhook
Calls a webhook. Used to integrate external systems or third party platforms. On top of sending the device's location (if triggered by device), it is possible to extend the webhook with custom fields; headers and values.
Example body:
{
"test":true,
"type":"MAN_DOWN",
"time":"1728588807",
"device":{
"id":1234,
"name":"My device name",
"type":"Twig One",
"industry":"Home address",
"operatingAddress":"Mainstreet 1",
"tempAddress":"Outside the bank",
"tempAddressExpiration":"1728588807",
"imei":"12345678910",
"uniqueId":"12345678910",
"phone":"+31600000000",
"extraFields":{
}
},
"account":{
"id":1234,
"name":"My customer"
},
"location":{
"serverTime":"1723566942",
"fixTime":"1723566943",
"latitude":51.4419056,
"longitude":5.4096687,
"beacons": [],
"beacon":"Office",
"geofences":"Home geofence",
"url":"https://maps.google.com/?q=51.4419056,5.4096687",
"liveUrl":"https://app.cuebly.com/alarm-location/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA#",
"tempUrl":"https://app.cuebly.com/live-location/BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB#"
}
}You must specify the following fields.
HTTP method - POST or GET
URL - Must be anything except referring back to Cuebly
Wait for possible new location - explained here
Include live location URL - When checked, the webhook will include a temporary URL with the live location of the device that is available for 24 hours
Extra headers - Add your own custom headers for when your application needs additional header information
Use custom body - When checked, you get an additional text area where you can provide your own body. Otherwise the scenario action will POST/GET the default body.
¶ Send assistance request
Sends an assistance request to the selected device(s) and/or the device(s) in the selected team(s) and/or geofence(s).
Sends an email to the configured recipients.
¶ Change geofence presence
Changes the presence of the device that triggered this scenario as per configuration in this action.
If you select All geofences, it will affect all geofences that the triggering device is connected to.
If make a selection, only the selected geofences will be affected, given that the device is also connected to the geofence.
¶ Create generic alarm
For some triggers, it is possible to escalate the event to an alarm. This is called a generic alarm. It is possible to create follow-up scenarios with the generic alarm trigger.
¶ Send to ARC
Available for alarm events. The alarms will be sent to the connected ARC.
¶ Multi-tenant
When having multiple customer accounts, you can trigger scenarios in account B by creating a multi-tenant action in account A. A unique code will be generate that is to be provided in the multi-tenant scenario in account B that should be triggered.
¶ Set digital I/O
Sets a digital output in a device that supports digital I/O.
¶ Resend last text message
Sends the last-sent text message again to the device. Convenient for when there is no local history of received messages.
As stated in the alert, the message will be sent with whatever parameters were used with the original message. This also means that when the message was sent without forced parameters, the message was sent with the configured “device defaults” from the device configuration.
If you leave the checkbox unchecked and the message parameters are different the second time, it is possible your “device defaults” have been changed by someone.
If you check the checkbox, you are able to force different parameters. For example, you may choose to receive it silently.
¶ Toggle timer
Start or stop timer alarms on devices that support timer alarms.
¶ Wait for possible new location
There is a special checkbox for when you use location placeholders in your text or use specific other scenario actions.
This is an example:
Because the placeholder {{beacon}} is used, you have the option:
- Leave the checkbox unchecked - this will try to use the last known position. This is convenient for when the device is tracking periodically and speed is important.
- Check the checkbox - this will pause the action, request a new position from the device, and wait until a new position is received before this action is executed. This is used in most cases, where you only need a new position when a critical event has occurred.
Remember that checking this checkbox results in some delay.
Last, when the device does not return a new position within 60 seconds, the given placeholder value is used (being [?] in the example above).
¶ Placeholders explained
¶ Placeholders in messages
<We are working on this wiki section>
¶ Geofence
This placeholder can have 2 functions.
In case of a geofence scenario (like geofence enter or geofence exit), it will display the name of the geofence the device is entering or leaving.
In other cases, it will display the name of the smallest geofence in which the device is currently present.
¶ Live location URL
This placeholder will create a URL that shows the live location of the device. This URL will expire in 24 hours and after that, it is no longer possible to open this URL.
Be careful who you are sharing this URL with, since it shares the location of your customer/colleague publicly for an amount of time.
A example use-case is to share the location of an elderly home resident leaving the premises (geofence), and you wish to find the person.
¶ Custom address
The custom (temporary) address of the triggering device. A custom address that can is stored for only 24 hours. This can be used for when positioning is not accurate and the user is at a specific address. When the value is expired, it will show up empty.
¶ Placeholders in recipients
It is possible to use contacts as recipients for voice/SMS messages or emails.
To use this function, make sure you have at least one contact.
Select the address book on the right of the recipient input and select your contact. You will only see the contacts that are applicable for the selected scenario action. In the example below, it will only show contacts that have a valid email address provided.
¶ Considering availability
Some contacts have a limited availability. You can optionally configure the scenario action to perform only when the recipient is actually available.
In this example below, the Security front desk is available only during office hours. The action will not be performed outside of office hours.
