Skip to main content

Create Your Own Transformer

Build custom transformers for validation, enrichment, or redaction.

The transformer interface

Transformers are functions that receive a context object and return a transformer instance:

Loading...

The context contains:

Loading...

The returned instance must implement:

Loading...

Return values

ReturnBehavior
{ event }Continue chain with modified event
voidContinue chain, event unchanged
falseStop chain, event dropped
{ event, next }Redirect to a different chain (fan-out)
{ event, respond }Continue chain with wrapped respond function

Minimal example

Loading...

Push context

The push function receives an event and a push context:

  • config: Transformer configuration
  • env: Environment dependencies
  • logger: Scoped logger for output
  • id: Transformer identifier
  • collector: Access to collector instance
  • ingest: Request metadata from source (optional)
Loading...

Examples

Enrich: add server-side data

Loading...

Validate: custom check

Loading...

Using your transformer

Loading...

Testing

Loading...

Package convention

Every walkerOS package includes machine-readable metadata for tooling and discovery.

walkerOS field in package.json

Loading...
FieldRequiredDescription
walkerOSYesObject with type metadata (and platform for sources/destinations)

Build-time generation

Use buildDev() from the shared tsup config to auto-generate walkerOS.json:

Loading...

This file contains your package's JSON Schemas and examples, enabling MCP tools and the CLI to validate configurations without installing your package.

Optional: Hints

Packages can export a hints record from src/dev.ts to provide lightweight, actionable context beyond schemas and examples, such as validation behavior, enrichment patterns, or troubleshooting tips. Hints are serialized into walkerOS.json and surfaced via MCP tools. See the walkeros-create-transformer skill for details.

Publishing checklist

  • walkerOS field in package.json
  • Keywords include walkeros and walkeros-transformer
  • buildDev() in tsup.config.ts
  • dist/walkerOS.json generated on build
  • npm run test passes
  • npm run lint passes

Next steps

💡 Need implementation support?
elbwalker offers hands-on support: setup review, measurement planning, destination mapping, and live troubleshooting. Book a 2-hour session (€399)