Skip to main content
Prompts ERP to Feishu Data Mapping Integrator

developer software_engineering template risk: medium

ERP to Feishu Data Mapping Integrator

The prompt instructs the model to act as an ERP Integration Specialist tasked with designing a solution to map ERP data fields (cost contracts, expenses, settlement sheets, payment…

  • Policy sensitive
  • Human review
  • External action: high

PROMPT

Act as an ERP Integration Specialist. You are tasked with designing a solution to map ERP system data fields to Feishu's multi-dimensional data tables. Your objectives include:

1. Analyzing the current ERP data structure, including cost contracts, expenses, settlement sheets, payment slips, and milestone nodes.
2. Designing a field mapping strategy to efficiently transfer data into Feishu tables.
3. Implementing functionality for batch operations such as adding, modifying, and deleting records.
4. Ensuring proper permissions management for data access and operations.
5. Providing a detailed technical plan, complete with code examples for implementation.

You will:
- Outline the business requirements and goals.
- Develop a technical architecture that supports the integration.
- Ensure the solution is scalable and maintainable.
- Provide sample code snippets demonstrating key functionalities.

Rules:
- Focus on security and data integrity.
- Consider performance optimizations.
- Use industry best practices for API integration.

Variables:
- ${erpDataStructure}: Description of the ERP data fields.
- ${feishuApiKey}: API key for Feishu integration.
- ${batchOperationType}: Type of batch operation (add, modify, delete).

INPUTS

erpDataStructure REQUIRED

Description of the ERP data fields.

feishuApiKey REQUIRED

API key for Feishu integration.

batchOperationType REQUIRED

Type of batch operation (add, modify, delete).

e.g. add

REQUIRED CONTEXT

  • ERP data structure description

ROLES & RULES

Role assignments

  • Act as an ERP Integration Specialist.
  1. Focus on security and data integrity.
  2. Consider performance optimizations.
  3. Use industry best practices for API integration.

EXPECTED OUTPUT

Format
structured_report
Constraints
  • include code examples
  • focus on security and data integrity
  • ensure scalability and maintainability
  • use industry best practices

SUCCESS CRITERIA

  • Outline the business requirements and goals.
  • Develop a technical architecture that supports the integration.
  • Ensure the solution is scalable and maintainable.
  • Provide sample code snippets demonstrating key functionalities.
  • Analyze the current ERP data structure including cost contracts expenses settlement sheets payment slips and milestone nodes.
  • Design a field mapping strategy to efficiently transfer data into Feishu tables.
  • Implement functionality for batch operations such as adding modifying and deleting records.
  • Ensure proper permissions management for data access and operations.
  • Provide a detailed technical plan complete with code examples for implementation.

FAILURE MODES

  • May generate generic solutions without specific ${erpDataStructure}
  • May overlook security and data integrity despite rules
  • May not adequately address performance optimizations
  • May fail to ensure scalability and maintainability
  • May not handle batch operations correctly based on ${batchOperationType}

CAVEATS

Dependencies
  • ${erpDataStructure}: Description of the ERP data fields.
  • ${feishuApiKey}: API key for Feishu integration.
  • ${batchOperationType}: Type of batch operation (add, modify, delete).
Missing context
  • Programming language for code examples
  • Detailed Feishu table schemas
  • Expected formats for variable values like ${erpDataStructure}

QUALITY

OVERALL
0.89
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.95
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Specify the programming language for code snippets, e.g., 'Provide code examples in Python using Feishu APIs'.
  • Add an output format section, e.g., 'Structure response with: 1. Business Requirements, 2. Technical Architecture, 3. Field Mapping Table, 4. Code Snippets, 5. Security & Performance Considerations'.
  • Clarify expected input format for variables, e.g., '${erpDataStructure} as JSON schema'.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER