Configure Celigo imports with adaptorType, field mappings, and operation logic.
npx skills add https://github.com/celigo/ai --skill configuring-imports
Please help me install this Agent Skill. Skill: configuring-imports Source: https://github.com/celigo/ai/tree/main/skills/configuring-imports Command: npx skills add https://github.com/celigo/ai --skill configuring-imports
This Skill helps you configure Celigo imports so upstream records can be written to the right destination system with correct mapping, operation logic, and optional AI-safe handling.
adaptorType and adaptor config block.Example: Configure an import that writes transformed customer records from a flow into a REST API, performs upsert based on an existing ID, and uses postSubmit to log results and pass enriched fields downstream.
Create a new import JSON that sets name, adaptorType, and the appropriate adaptor block (for example http{}, rdbms{}, s3{}, or ai agent config), then add Mapper 2.0 mappings and an operation/upsert strategy that matches your destination behavior.
High-intent search queries and answers about installing and using this skill.
To configure upsert logic for Celigo imports, you set the operation strategy to create, update, or upsert based on an existing ID within the import JSON. This ensures upstream records are written to the destination system with correct mapping and sync behavior using Mapper 2.0 or Mapper 1.0.
preMap, postMap, and postSubmit pipeline hooks are deterministic stages used to inject custom logic during data destination imports. They allow you to transform records before mapping, modify data after mapping, and execute post-submit tasks like logging results or passing enriched fields downstream.
Yes, Celigo imports support writing records to REST APIs, databases, ERPs, files, and AI models. You must set the correct case-sensitive adaptorType—such as http or rdbms—and configure the appropriate adaptor block to target your specific destination system.
One-to-many fan-out allows a single upstream record to generate multiple records in the destination system during import. It is controlled by the operation logic and field mappings, enabling complex data distribution alongside standard CRUD operations like create, update, delete, attach, and detach.
Yes, AI agent imports and file generation require specific adaptor types and configuration blocks within the Celigo import JSON. You must configure the ai agent block or file-based adaptor to handle record-to-file generation and AI agent or guardrail invocation properly.
The best way to handle response mapping is to plan it within the import configuration to pass enriched fields downstream. By utilizing postSubmit pipeline hooks, you can capture destination responses and map them for subsequent steps in the integration flow.
intuitemGuide new users through initial CISO Assistant setup using MCP server tools.
Eva813Map UI fields to OpenAPI endpoints and generate TypeScript state models.
celigoWrite Celigo Mapper 2.0 and Transformation 2.0 field mappings with JSONPath extracts.
RektooooooPersist Swift app data using file-based and SQLite storage.