Blueprints would be pre-made configurations where you only need to set the configurations that might differ.

It would basically be a config export of the total automation which can either be configured using it's own fieldset or be imported into SyncEngine using this fieldset configuration.

Any format that allows nested arrays should be supported (YML, JSON, etc.)

• Create BlueprintModel > Format to Model conversion service.
• Blueprint React controller
• Blueprint importer (module)
• Blueprint updater with version control (module)

Discussion

• Should we create a separate root folder for all installed blueprints? >> YES
• How to handle persistent data like datasets? >> Create entity and lock it as blueprint related.
• Should we expand blueprints to Steps? >> Yes
• Should we expand blueprints to Flows >> No