¶ Helper Libraries
The Helper Libraries section provides reusable C# utilities designed to streamline development and reduce boilerplate when building custom logic on the Fuse platform.
These libraries offer composable capabilities that would otherwise require significant development effort — enabling faster creation of integration connectors, interoperability providers, and other artifacts that extend the platform.
They belong to the System domain and are commonly used inside pipeline components, orchestration steps, and API integrations.
¶ Purpose
- Accelerate development by offering reusable abstractions for common tasks
- Enable rapid creation of platform extensions such as custom connectors or orchestration helpers
- Reduce duplication and promote standardization across teams
- Provide tooling that complements Fuse’s domain frameworks and execution layers
¶ When to Use a Helper Library
Use a helper when:
- You’re building reusable components or integration artifacts
- You want to avoid rewriting complex request or response formatting logic
- You need common utilities to interact with APIs, workflows, tokens, or orchestration metadata
- You’re implementing orchestration logic that spans multiple layers or domains
¶ Available Helpers
| Helper Name | Purpose | Link |
|---|---|---|
| GraphQL Builder | Construct GraphQL operations with query, mutation, upload, and variable support using a fluent builder model | View |
Additional helpers will be published over time — supporting token construction, multipart form handling, and metadata generation.
¶ How Helpers Fit in the Fuse Platform
Helper libraries are domain-agnostic and designed to support development across:
Pipeline components
Integration connectors
Custom route handlers
Orchestration logic
Automation triggers
They do not enforce specific domain constraints, making them reusable across multiple runtime contexts.
¶ Development Platform
All helper libraries are written in C# and target the .NET Framework platform used by the Fuse runtime.
¶ Contributing a Helper
To contribute or propose a helper:
- Clearly define the problem it solves (e.g., signature normalization, payload formatting)
- Ensure it is broadly applicable and not bound to a single integration
- Include:
- Clean, namespace-scoped implementation
- XML documentation for all public members
- At least one usage example (code or markdown)
- Tests (optional but preferred)
Once approved, helpers will be published here and versioned for reuse.
Next: GraphQL Builder — Construct GraphQL operations with fluent configuration and file upload support.