Integration Mapper
Categorizing mappings by complexity (direct, transform, computed) prioritizes implementation effort. The test checklist prevents going live with untested edge cases.
Map data between {{system_a}} and {{system_b}} to build an integration.\n\nSystem A schema:\n{{schema_a}}\n\nSystem B schema:\n{{schema_b}}\n\nIntegration direction: {{direction}}\n\nGenerate a complete field mapping:\n\n| System A Field | System B Field | Transform | Notes |\n|---|---|---|---|\n\nFor each mapping:\n- **Direct**: Fields that map 1:1 with no transformation\n- **Transform**: Fields that need conversion (date formats, units, enums)\n- **Computed**: Target fields that require combining multiple source fields\n- **Unmapped source**: Source fields with no target equivalent (log and skip)\n- **Missing required**: Target required fields with no source data (provide defaults)\n\nAlso provide:\n1. Sample request/response payloads for the integration\n2. Error handling for each transformation that could fail\n3. A test checklist: specific data scenarios to validate before going live
Variables to customize
Why this prompt works
Categorizing mappings by complexity (direct, transform, computed) prioritizes implementation effort. The test checklist prevents going live with untested edge cases.
What you get when you save this prompt
Your workspace unlocks powerful tools to iterate and improve.
AI Optimization
One-click improvement with structure analysis and pattern suggestions.
Version History
Track every edit. Compare versions side-by-side with word-level diffs.
Folders & Tags
Organize your library with nested folders, tags, and drag-and-drop.
$ npm i -g @promptingbox/mcpUse Everywhere
Access prompts from Claude, Cursor, ChatGPT & more via MCP integration.
Your prompts, organized
Save, version, and access your best prompts across ChatGPT, Claude, Cursor, and more.