Coordinates Celigo flows with page processors, routers, branching topology and error management.
npx skills add https://github.com/celigo/ai --skill building-flows
Please help me install this Agent Skill. Skill: building-flows Source: https://github.com/celigo/ai/tree/main/skills/building-flows Command: npx skills add https://github.com/celigo/ai --skill building-flows
Building Celigo integrations requires assembling exports, imports, processors, routers, and schedules into a correct, maintainable flow—so this Skill helps you design, structure, and debug end-to-end data movement reliably.
Use the building-flows Skill to create a scheduled flow that reads data from configured exports, routes records conditionally through processors, and handles errors safely during imports.
High-intent search queries and answers about installing and using this skill.
To build a Celigo integration flow with routing, you configure exports to read source data and use routers to branch records to specific page processors based on defined conditions. This enforces mutual exclusivity between page processors and routers.
Linear Celigo pipelines pass data sequentially through page processors, while branching pipelines use routers to direct records down different processing paths. You choose between them based on whether your data requires conditional routing.
You create reusable Celigo flow templates by designing abstract flow blueprints and deploying per-tenant or per-environment instances using overrides. This allows you to maintain a single base structure across multiple deployments.
Celigo flow validation fails on reference errors when integration, export, import, or connection identifiers are invalid. You must verify that all configured identifiers correctly match existing account patterns before deployment.
To handle errors and schedule data pipelines in Celigo, you apply error management configurations during imports and set up scheduling triggers. This ensures your pipelines move data safely at designated times or events.
No, you cannot use page processors and routers within the same Celigo flow branch. The system enforces mutual exclusivity between these two components to maintain a clear and predictable processing topology.
lyticsConfigure end-to-end data integrations with authentication, connections, and jobs.
riftzen-bitMonitor deployed URLs for HTTP status, console errors, performance metrics, and API health.
Adonis0123Aggregate UI/UX guidelines, patterns, and color/typography data into a Master.md design system.
celigoImplement Celigo JavaScript hook functions for pipeline control and routing with strict I/O contracts.
