Automation nodes

Node types

Each definition belongs to one plugin feature. BlokeBot rejects work from an old plugin worker or disabled feature.

• The editor supports plugin source and action nodes.
• It supports plugin value and control nodes.
• It supports plugin transform nodes.

source

Starts a flow and returns declared output values.

action

Uses declared input values to perform an allowed effect.

value

Returns a value from its configuration and input values.

control

Uses declared input values to control the progress of a flow.

transform

Converts declared input values into declared output values.

Ports

Each input and output declares a value kind and whether the value is required. The generator creates the corresponding Lua handler type.

string

A string value.

number

A finite number value.

boolean

A true or false value.

array

An ordered list of plugin values.

map

A string-keyed map of plugin values.

Definitions

[[automationDefinitions]]
id = "store-submission"
featureId = "collection"
kind = "action"
name = "Store link submission"
description = "Stores one submitted link."
module = "queue"
entryPoint = "store_submission"
outputs = []

[[automationDefinitions.inputs]]
id = "url"
name = "URL"
valueKind = "string"
required = true

Templates

Each feature lists the templates that it owns.

BlokeBot validates the graph before feature enablement.

• Invalid ports prevent enablement.
• Duplicate writers prevent enablement.
• Missing inputs prevent enablement.
• Cycles prevent enablement.
• A template defines nodes.
• A template defines configuration.
• A template defines typed data edges.

[[automationTemplates]]
id = "queue-submission"
featureId = "collection"
name = "Queue submitted links"

[[automationTemplates.nodes]]
id = "store"
definitionId = "store-submission"
configuration = { kind = "map", properties = [] }

Generated flows

• One transaction creates a valid flow during feature enablement. It records which plugin and template created the flow.
• Repeated recovery does not create a duplicate flow.
• BlokeBot does not overwrite or rename a conflicting host flow.
• If a user deletes the generated flow, a later feature disablement and enablement can create it again.
• A plugin update replaces the current node definitions and handlers.
• Plugin removal deletes plugin definitions and dependent flows.
• Plugin removal deletes nodes and run history.
• Plugin removal deletes ledgers and source receipts.

Updates and disabled features

An old worker result cannot start or complete a run. Feature disablement and plugin removal cancel affected calls and runs.

• Before each automation call, BlokeBot checks the plugin.
• Before each automation call, BlokeBot checks the host.
• Before each automation call, BlokeBot checks the feature.
• Before each automation call, BlokeBot checks the node definition.
• Before each automation call, BlokeBot checks the active installation.