Overview
Modules are reusable subgraphs that appear as a single node in a workflow. You create and manage your modules from the Modules page in the platform scope. From there you can create a new module, build its internal workflow, expose inputs and outputs via the Module I/O panel, and then use the module in any workflow like any other node. For an introduction to what modules are and how they fit with workflows and the Library, see Modules in Key Concepts.Where to Find Your Modules
All of your modules are listed on the Modules page. In the sidebar, under the PLATFORM section, click Modules. The page shows a grid of your modules with search and filters. Use + Create Module in the top right to create a new one.Creating a Module
Open the Create Module dialog
On the Modules page, click + Create Module in the top right. A dialog opens asking for the module name and an optional description.
Enter name and description
Enter a Name for the module. You can add a Description (optional) to explain what the module does (up to 140 characters). The dialog also links to the Trickest documentation for more guidance.
Building the Module
Build the module like any other workflow. Add and connect nodes (tools, scripts, and optionally other modules) on the canvas. The Module I/O panel appears to the left of the canvas. When the module is new, it shows No inputs exposed yet and No outputs exposed yet; the module does not expose any inputs or outputs until you define them.Defining Module Inputs and Outputs
After the module has been executed, the Module I/O panel shows an Available section that lists:- Inputs from the nodes in the module that can be exposed as module inputs.
- Outputs from the nodes in the module that can be exposed as module outputs.
Add from Available
In the Module I/O panel, find the input or output you want under Available and click the + button next to it (for outputs, the tooltip may say “Expose as module output”).
Name the input or output
Give the input or output a custom name (recommended) or keep the default. A custom name makes the module easier to use when you add it to other workflows.