writing-mappings

Write Celigo Mapper 2.0 and Transformation 2.0 field mappings with JSONPath extracts.

3|2|Updated May 20, 2026
One-click install
npx skills add https://github.com/celigo/ai --skill writing-mappings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-mappings
Source: https://github.com/celigo/ai/tree/main/skills/writing-mappings
Command: npx skills add https://github.com/celigo/ai --skill writing-mappings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write and troubleshoot Celigo integration mappings so your data transforms correctly between systems instead of failing silently or producing incorrect field shapes.

Core Features & Use Cases

  • Mapper 2.0 (imports): Build recursive mappings[] for nested objects/arrays using correct generate, dataType, and extract rules.
  • Transformation 2.0 (exports): Reshape export payloads with rule-based transform configurations in create/modify modes.
  • Lookups + response mapping: Apply value translation via lookups[] and carry data back into records using response mapping syntax for flow pageProcessors[].
  • Version-aware guidance: Use Mapper 2.0 syntax for mappings[] and Mapper 1.0 syntax for mapping.fields[]/mapping.lists[] (NetSuite/Salesforce) without mixing them.
  • Validation guardrails: Includes practical checklists to avoid common configuration errors such as dot notation in generate, missing status: "Active", missing buildArrayHelper, and incorrect array path handling.

Quick Start

Ask an AI to convert your desired source-to-target field structure into the correct Mapper 2.0 mappings[] JSON using JSONPath extracts, including lookups and array buildArrayHelper where needed.

Frequently Asked Questions about writing-mappings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Celigo data mappings for nested arrays in Mapper 2.0?

To write Celigo data mappings for nested arrays in Mapper 2.0, construct recursive mappings using correct generate, dataType, and extract rules alongside a buildArrayHelper to reliably reshape source data into the target structure.

What is the correct syntax for lookups and response mapping in Celigo integrations?

Lookups in Celigo integrations apply optional value translation with fallback behavior via lookups, while response mapping carries data back into records using specific syntax within flow pageProcessors to ensure accurate field carry-back.

Why are my Celigo field mappings failing silently during data transformation?

Celigo field mappings often fail silently due to configuration errors like using dot notation in generate paths, missing Active status fields, missing buildArrayHelper for arrays, or mixing Mapper 1.0 and Mapper 2.0 syntax.

Can I use Transformation 2.0 to reshape export payloads in Celigo?

Yes, you can use Transformation 2.0 to reshape export payloads in Celigo by applying rule-based transform configurations in create or modify modes to correctly translate and restructure output data.

Does Celigo Mapper 2.0 support root-relative JSONPath for data extraction?

Yes, Celigo Mapper 2.0 supports root-relative JSONPath extracts to define precise data extraction paths, ensuring source fields are accurately mapped to the required target structure without relative path errors.

When should I use Mapper 2.0 syntax instead of Mapper 1.0 in Celigo?

Use Mapper 2.0 syntax for mappings arrays and Mapper 1.0 syntax for mapping.fields or mapping.lists in NetSuite or Salesforce, ensuring you never mix the two versions within the same integration configuration.