Beebotte Beerules are
action rules that allow to create business logic on messages as they go through Beebotte network.
When Beebotte receives a message or an event corresponding to a Beerule trigger, the Beerule condition gets evaluated. If the condition is satisfied, then the Beerule action is executed.
Beerules allow to:
webhookswhen specific events happen
A Beerule is composed of three parts:
trigger can be any message or connection event including:
publisha message being published to a given channel
writea message written to a given channel resource
connecta WebSocket or MQTT client connection to a user's account
disconnecta client disconnection
subscribea Websocket or MQTT subscription event to a channel
unsubscribean unsubscribe event from a channel/resource
joina Websocket subscription to a presence channel
leavean unsubscribe event from a presence channel
condition optional condition to be satisfied in order for the rule's action to be executed. The condition is a true/false expression applied on the event data or metadata.
action an action to perform if the condition is satisfied. It can be one of:
writewrites a message to a given Beebotte channel/resource
publishpublishes a message to a given channel/resource
webhookcalls a webhook on an external system. This enables integration with a wide set of applications.