Elements of the Flow
Trigger
Triggers are events that can start a flow.
Name | Description |
---|---|
Alarm triggered | This trigger starts a flow when an alarm has been triggered in the organization. |
Alarm closed | This trigger starts a flow when an alarm in the organization has been closed. |
DWD weather warning | This trigger starts a flow when a DWD weather warning with the properties configured in the trigger is present. Details about the trigger for DWD weather warnings can be found here. |
Email received | This trigger starts a flow when an email has been received. Details about the trigger email received can be found here. |
Event triggered | This trigger starts a flow when an event has been triggered in the organization. |
Event closed | This trigger starts a flow when an event has been closed in the organization. |
HTTP trigger | This trigger starts a flow when an HTTP call is made to the specified URL. Details about the HTTP trigger can be found here. |
IMAP trigger | The IMAP trigger starts a flow when a new mail is received in a configured mailbox. Details about the IMAP trigger can be found here. |
Tag triggered | This trigger starts a flow when one of the stored tags has been triggered. |
Websocket trigger | This trigger is used to start a flow when new data is received via a websocket interface, like KATSYS. |
Alarming
These elements can be used to trigger or edit alarms and events.
Name | Description |
---|---|
Trigger alarm | Triggers an alarm with the configured resources. |
Format alarm | Formats the details of an alarm with the configured string. Details about the format alarm element can be found here. |
Load alarm | Loads the current details of an alarm. |
Cancel event | This element can be used to specifically cancel a defined event. |
Create event | Opens a new event. |
Close event | Closes an open event. |
Search event | Searches for an event within the organization. Details about the search event element can be found here. |
Trigger tag | Triggers a tag and the associated alarms in sub-organizations. |
Communication
Elements that enable communication.
Name | Description |
---|---|
Send e-mail | Sends an e-mail to the deposited recipients. |
Send fax | Sends a stored document by fax to the specified phone number. |
HTTP client | Sends an HTTP call to the specified URL. |
Send messenger message | Sends a message in the messenger to a chat room. |
Send message to pager | Sends a message to one or more pagers. |
Processing
Parser that allows filtering information.
Name | Description |
---|---|
JSON parser | Processes JSON input into configured variables. Details about the JSON parser can be found here. |
Text parser | Processes text input into configured variables. Details about the text parser can be found here. |
XML parser | Process XML input into configured variables. Details about the XML parser can be found here. |
Text
Allows merging data for further processing.
Name | Description |
---|---|
JSON string | This element allows to create a JSON string. |
Merge strings | Dynamically merge multiple strings using custom variables. |
Control
Allows to control the data to be processed.
Name | Description |
---|---|
Check for one or more strings | Similar to the check for string element. Checks whether one or more specified strings are contained in a function result. Details about the check for one or more strings element can be found here. |
Check for string | Checks whether a specified string is contained in a function result. Details about the check for string element can be found here. |
Conditional variable | This element allows to use variables depending on conditions, for example to associate different deployment keywords with a scenario ID. |
Waiting | This function delays the execution of the next function by the specified seconds. |
Updated on: 26/05/2023
Thank you!