Home

or Stripe directly

This module helps you generate triggers by pairing events with conditions and actions. You can find the menu to create the triggers in the settings.

Trigger

A trigger is a workflow blueprint composed of different nodes connected to each other and triggered by an event.

Sub-Trigger

A sub-trigger is a subset of a trigger not associated to any node event, it can be used in regular triggers as a node.

Node

A node is the representation of a piece of logic within the module, nodes call on each other for execution or data query.

Bridges

Bridges are simple connections between nodes which carry no context or data, they are only there to order the execution of nodes. All nodes (excluding variable & value nodes which are queried and never executed) have an in bridge and most of them have a out while others have more complex output bridges to branch out depending on the resulting logic of the executed node.

Inputs

Inputs are entries/connections used to feed data into a node, they can either be directly provided via their field (if any) or by linking to the output of another node.

Outputs

Outputs are connections that provide data to be used by other nodes, the data depends on the state of the node logic when and only if it was executed.

Module Triggers Registration

Module can register their own triggers which avoids the need for users to have to import them manually. To do so, a relative path to a json file must be provided in the module.json manifest.

"flags": {
    "<module-id>": {
        "triggers": "relative/path/to/triggers.json"
    }
},

The json file must be a direct export from the module without any change. Only triggers and subtriggers will be used from it, so there is no point in selecting items when exporting the data as it would only increase load time.

Note

Each module has its own isolated triggers context, there is no relation possible between them or with your world triggers.

Note

Module triggers are all disabled by default.