How To Call It
Event is a global table: call its functions with a dot (Event.<method>(...)), not a colon.
Reads one field of the trigger context ("title", "body", "package", or "extra.<key>" for system broadcast extras).
Documented for app version 1.0.51Updated:
Event is a global table: call its functions with a dot (Event.<method>(...)), not a colon.
In system flow, design steps as observe first and act second when the API can affect device state.
Required: key. Returns a Lua value of whatever type was stored or read.
Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.
The snippet below is a starter pattern that can be applied directly in runtime flow.
local result = Event.get("title")From foundation to combined usage, each level is provided as a separate code block so you can copy the level you need and adapt it directly.
local result = Event.get("title")local stepOk = true
local result = Event.get("title")
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
local result = Event.get("title")
end)
if not ok then
print("API step failed: Event.get: " .. tostring(err))
requestStop()
end-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_get_step()
local result = Event.get("title")
end
local ok, err = pcall(run_get_step)
if not ok then
toast("Step failed")
print(err)
endlocal result = Event.get("title")
wait(200)
print("Combined with logging and flow control")