Skip to main content

Overview

Field Mappings define how your custom schema fields translate to gu1’s unified entity model. Each mapping can include transformations to format, calculate, or conditionally process data during import.
Mappings bridge the gap between your data structure and gu1’s entity model, enabling seamless data ingestion from any source.

Create Field Mapping

Create a mapping configuration for your custom schema.

Request Body

Mapping Data Object

Field Mapping Object

Response

Transformation Types

Direct Mapping

Copy value as-is with no changes:

Format Transformation

Apply string, date, or number formatting:
Common Format Examples:

Calculate Transformation

Perform mathematical calculations:
Common Calculate Examples:

Conditional Transformation

Apply if/then logic:

Lookup Transformation

Look up values from reference tables:

Custom Transformation

Execute custom JavaScript:
Custom transformations have security restrictions. Only whitelisted JavaScript functions are allowed.

Validation Rules

Configure validation behavior:

Transformation Settings

Configure processing behavior:

List Mappings

Get all mapping configurations for your organization:

Response

Get Mapping

Retrieve a specific mapping configuration:

Response

Update Mapping

Update an existing mapping configuration:

Request Body

Delete Mapping

Delete a mapping configuration:

Complete Example: Banking Customer Mapping

Error Responses

Validation Error

Transformation Error

Best Practices

  • Begin with direct mappings for most fields
  • Add transformations only when necessary
  • Test each transformation individually
  • Gradually increase complexity
  • Test mappings with sample data before production
  • Validate edge cases (null, empty, invalid values)
  • Monitor transformation errors in logs
  • Use strictMode in production environments
  • Set appropriate defaultValue for optional fields
  • Use validationRule for complex validations
  • Apply format transformations for consistency
  • Handle missing/null values explicitly
  • Avoid complex custom transformations in hot paths
  • Use batch processing for large datasets
  • Set reasonable timeout values
  • Monitor transformation execution times

Next Steps

Smart Field Detection

Auto-generate mappings from sample data

Import Entities

Use mappings to import entity data

Data Mapping Guide

Complete workflow guide

Transformations Guide

Advanced transformation patterns