Create a reusable Orbit module
Define a reusable Orbit module with fields, grouping, and an agent job.
Last updated 16 September 2026
Define a reusable Orbit module with fields, grouping, and an agent job.
Before you start
Choose one repeatable information need, such as an analytics event lexicon. Decide which field uniquely identifies a record and whether grouping is useful.
The Analytics template provides a starting structure. Review its fields and agent job before saving and adding it to a project.
Step by step
Open Settings → Orbit → Add new module. Choose Analytics template for a starting example or Blank module for a new structure.
Give the module a clear Name and Description that explain what its records represent.
Review the grouped-table view and Section field. Use a section such as Area when records should appear under meaningful headings.
Define the fields and their types. The first field is the required record identity; use short text, long text, or list according to the information.
Write the Agent job as concrete instructions: what to inspect, what to maintain, and what requires a decision. Check the template’s assumptions before reusing it.
Save module, return to a project, and add it through Orbit → Add.
Create one example record and try a narrowly scoped agent request before using the module for a larger workflow.
What to expect
The module definition is available to projects, with a structure and agent job that match its intended use.
Troubleshooting and useful details
The screenshot shows the Analytics template before saving. Defining a job does not run an agent. Later definition changes can affect projects using the module, so review field meaning and existing records before restructuring it.
