configuring-exports

Configure Celigo export configurations for record-based APIs, file transfers, and listeners.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design Celigo export (data source) configurations that reliably pull records, perform lookup enrichment, and handle common execution details like resourcePath extraction, filtering, and delta/incremental sync.

Core Features & Use Cases

  • Configure export behavior for both source exports and lookup exports (isLookup: true), including one-to-many lookup patterns.
  • Choose the right adaptor type and category (listeners, file transfers, record-based exports) using an adaptor decision matrix.
  • Implement export execution fundamentals: request/query/file read, response parsing via resourcePath, optional Transformation 2.0, output filters, and preSavePage hooks.
  • Handle operational readiness with schema-reading guidance and a checklist for correctness (adaptorType casing, required fields, delta rules, file parsing config, and common gotchas).

Quick Start

Create a new Celigo export by first selecting the correct adaptor type (HTTPExport, NetSuiteExport, FTPExport, etc.), then set the minimal required fields (name, adaptorType, and connection/adapter config), and finally confirm the record extraction resourcePath and any delta/incremental settings match your source responses.

Frequently Asked Questions about configuring-exports

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

FAQPage Schema
How do I configure Celigo exports to pull records from an external API?

To configure Celigo exports, select the correct adaptor type (like HTTPExport), set the required connection and adaptor config, and define the record extraction resourcePath to shape the API response for downstream flow steps.

What is the difference between a source export and a lookup export in Celigo?

A source export acts as the primary data source pulling records into a flow, while a lookup export uses isLookup: true to enrich those records by fetching additional related data from an external system during execution.

How do I set up delta sync for incremental data exports in Celigo?

Delta sync for incremental data exports requires configuring the delta rules within your adaptor settings so the export only fetches newly modified records, preventing duplicate data processing across flow executions.

How does resourcePath work when parsing Celigo export responses?

The resourcePath extracts the specific array of records from the parsed API response, ensuring the export returns the expected data objects in the correct execution order for downstream transformation and filtering.

Can I apply output filtering and transformations directly to Celigo exports?

Yes, Celigo exports support optional Transformation 2.0, output filters, and preSavePage hooks to shape the extracted records before they are passed to the next integration flow step.

What are common gotchas when configuring file transfer and listener exports in Celigo?

Common configuration gotchas include incorrect adaptorType casing, missing required connection fields, invalid file parsing config, and improperly configured delta rules that break operational readiness for listener or file transfer exports.