Automation workflows allow users to create a custom execution plan when certain events are triggered. Using this, they can create custom alarm mechanisms, tagging guests, etc.
Triggers
Triggers are pre-defined events in Starling that are triggered when certain things happen.
|
Name |
Description |
|
Manual |
It’s fired manually by clicking “Run” in the options menu. |
|
IoT Registered |
A BLE device is attached to a guest, e.g., Guest check-in for visitor management. |
|
IoT Unregistered |
A BLE device is detached from a guest, e.g., Guest check-out for visitor management. |
|
Location Update |
Fired when a guest location notification is received. Options
|
|
Zone Enter |
Guest has entered the specified zone. Options
|
|
Zone Exit |
Guest has exited the specified zone. Options
|
|
Button Press |
Guest has pressed the button on the BLE device. |
|
Sensor Data |
BLE sensor data is received and the conditions are met. If a condition value is left blank, it’ll be ignored. Options
|
|
Occupancy Alert |
Occupancy of a location is exceeded for the given capacity threshold. Options
|
|
Guest Connect |
Guest has connected to the SSID and has seen the splash page. |
|
Guest Sign In |
Guest has been granted internet access. |
|
Guest Sign Out |
Guest Wi-Fi connection session has ended (disconnected). |
|
Guest Detected |
Guest Wi-Fi signal is detected. It does not mean the guest has connected to an SSID or has internet access. |
|
Incoming Webhook |
It’s fired when an HTTP POST request’s sent to the callback URL which can be configured in the options. |
|
Presence End |
It’s triggered when a visitation ends. Options
|
|
Presence Start |
It’s triggered when a visitation starts. Options
|
|
Scheduled |
It runs according to the specified time and perform the actions in the automation workflow Options
Custom: It works with Cron expressions |
|
Zone Occupancy Alert |
Occupancy of a location and zone (if specified) is exceeded for the given capacity threshold. Options
|
Conditions
Condition nodes are used to check triggered events (trigger node) meet certain conditions in order to continue the execution of the workflow.
|
Name |
Description |
|
Timestamp |
Allows filtering events, based on their timestamp (time that event happened). Conditions
|
|
Location |
Allows filtering events, based on location(s) that it happened in. It offers multiple options how to check location. Not all events have guest information. Conditions
|
|
Guest |
Allows filtering events, based on features of guest that performed it. It allows many combinations to check guest’s features. Not all events have guest information. Conditions
|
Actions
Actions are used to perform a task on a certain point in the workflow.
|
Name |
Description |
|
|
Used to send an email. It allows to send email to initiator or custom recipients. Options
|
|
SMS |
Used to send a SMS message. It allows to send email to initiator or custom recipients. Options
|
|
Http Request |
Used to send a Http request to a URL with given parameters. Options
Basic Authentication: Username and Password Bearer Authentication: Bearer Token
|
|
Slack Message |
Used to send a Slack message to given user or channel. Options
|
|
Add Tag |
Used to add a tag guest who performed the event. Options
|
|
Remove Tag |
Used to remove a tag guest who performed the event. Options
|
|
Custom Action |
Used to perform the specified custom event Options
|
|
Pause |
Used to stop execution of the workflow for given period. Options
|
Comments
0 comments
Article is closed for comments.