Artifact Types
InstallHub can package five categories of BizFirstGO artifacts. Each type has a corresponding package type identifier used in the manifest and dependency declarations.
Supported Artifact Types
Workflows workflow-package
Process and thread definitions created in Flow Studio. Workflows define the execution logic of your automation — nodes, connections, expressions, and guard rails. A workflow package includes both ProcessDefinition records (top-level workflows) and ThreadDefinition records (sub-workflows and loops).
Dependency behavior: A workflow that uses Atlas Forms, entity schemas, or datasource configurations will cause those artifacts to be automatically pulled into the package during dependency resolution.
| Sub-type | Description |
|---|---|
ProcessDefinition | A top-level workflow with a start trigger and execution graph |
ThreadDefinition | A sub-workflow invoked from a parent process or loop node |
Atlas Forms form-package
Form definitions built in Atlas Forms Studio — including field layouts, validation rules, form actions, and field library references. A form package captures the complete form definition as serialized JSON along with any embedded SQL queries used by datasource-bound fields.
Dependency behavior: Forms that reference shared field libraries will cause those libraries to be included in the package automatically.
| Sub-type | Description |
|---|---|
AtlasForm | A complete form definition (schema, fields, actions) |
FieldLibrary | A shared collection of reusable field definitions |
FormGroup | A logical group of forms packaged together |
App Studio Apps app-package
Visual applications built in App Studio — dashboards, data grids, widgets, and navigation trees. App packages bundle the full App Studio JSON definition, including layout configuration, widget bindings, and action references.
Dependency behavior: Apps that embed Atlas Forms or call workflow APIs will include those dependencies in the package.
Octopus Agents agent-package
AI agent definitions created in the Octopus framework — including the agent's prompt configuration, memory type settings, tool bindings, and plugin configurations. Agent packages allow sharing AI capabilities across tenants.
Note: Agent packages do not include episodic memory contents — only the agent definition and configuration. Memory is tenant-specific and is not portable.
Configuration config-package
Rules, entity schemas, and application settings that support other artifacts. Configuration packages are typically included as dependencies in workflow or form packages rather than being published standalone.
| Sub-type | Description |
|---|---|
RuleSet | Business rule definitions evaluated by the rules engine |
EntitySchema | Custom entity definitions used by data nodes |
AppDefinition | App-level configuration (settings, theme, permissions) |
Dependency Types in the Manifest
The manifest's dependencies array uses these artifact type identifiers:
{
"dependencies": [
{ "type": "ProcessDefinition", "id": "proc-1001", "name": "OnboardingWorkflow", "version": "2.1.0", "hash": "sha256:abc..." },
{ "type": "AtlasForm", "id": "form-2005", "name": "EmployeeForm", "version": "1.0.0", "hash": "sha256:def..." },
{ "type": "RuleSet", "id": "rule-305", "name": "ApprovalRules", "version": "1.2.0", "hash": "sha256:ghi..." },
{ "type": "EntitySchema", "id": "ent-44", "name": "EmployeeSchema", "version": "1.0.0", "hash": "sha256:jkl..." }
]
}Which Artifact Type Should I Use?
Choose your package type based on the primary artifact you want to share:
- Sharing an end-to-end automation process? Use
workflow-package. - Sharing a reusable data entry form? Use
form-package. - Sharing a dashboard or UI application? Use
app-package. - Sharing an AI assistant or agent? Use
agent-package. - Sharing supporting rules or schemas only? Use
config-package.
In most cases, a workflow-package or form-package will automatically pull in the required config-package contents through dependency resolution — you rarely need to create config packages manually.