Skip to main content

Introduction to Mappers

A mapper in 1Gateway defines how messages are transformed between different formats.

It converts product-specific messages into normalized types (such as NormalizedIncident, NormalizedAlarm, or NormalizedMetric).

Each mapper contains one or more mappings, which define how message fields are transformed from one message type to another..

Mapper Concept Conceptual illustration: an External System Message passes through a mapper — containing individual mappings — and emerges as a Normalized Message.

When a message passes through 1Gateway — for example, between ServiceNow and SolarWinds — it’s first converted from the product’s native format (e.g., ServiceNow Message) into a normalized format.
A second mapper can then transform that normalized message into the target product’s format (e.g., SolarWinds Message).

Normalization enables scalability and interoperability, making it easy to add new systems without redesigning existing integrations.

note

Normalization is not required for 1Gateway to function, but it is highly recommended for long-term scalability and maintenance.

Mapping Types​

Mappings can perform a wide range of transformations, from simple field transfers to advanced logic:

  • Field-to-field translation: Copy or rename data between messages.
  • Formatting and conversions: Adjust timestamps, units, or data formats.
  • String operations: Replace, extract, or clean up text values.
  • Calculations and logic: Apply arithmetic or conditional expressions.
  • Data enrichment: Add context by retrieving information from external sources.