configuring-filters

Configure Celigo filter rules for exports, imports, and flow routing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you prevent bad, irrelevant, or incomplete records from clogging your Celigo AI-driven pipelines by applying precise filter rules at the right execution point.

Core Features & Use Cases

  • Record gating across the pipeline: Apply filters to export output, import input, lookup input filtering, and flow router branch routing so only intended records continue.
  • Expression-first filtering: Build fast, declarative S-expression rules using operators like equals, contains, empty/notempty, and logical combinators (and/or/not).
  • Script fallback for complex logic: Switch to script-based filters when you need multi-step conditions, date math, or custom evaluation that expressions cannot model.
  • Practical testing and debugging: Use job stats concepts like numIgnore to validate that filtered records are being skipped (not errored).

Quick Start

Add an expression output filter to your export so only records with a non-empty email continue into the flow.

Frequently Asked Questions about configuring-filters

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

FAQPage Schema
How do I filter records in a Celigo data pipeline so only specific rows are processed?

To filter records in a Celigo data pipeline, apply expression-based prefix S-expression rules using operators like equals, contains, and empty/notempty to determine which records continue processing versus being silently dropped.

What is the difference between expression filters and script filters in Celigo?

Expression filters in Celigo use declarative S-expression rules with logical combinators like and/or/not for fast evaluation, while script-based filters handle complex multi-step conditions, date math, or custom logic by returning strict true/false outcomes.

How do I route records through different flow branches based on conditions in Celigo?

To route records through different flow branches in Celigo, configure filter rules on the flow router branch using expression-based S-expression conditions or script-based filters that evaluate each record and direct it to the matching branch.

Can I use Celigo filters to avoid unnecessary lookup calls for incomplete data?

Yes, you can apply lookup input filtering in Celigo to prevent unnecessary lookup calls when input records are incomplete, ensuring only records with required fields present trigger the lookup operation and reducing wasted API calls.

Why are my filtered records showing as ignored instead of errored in Celigo job stats?

Filtered records in Celigo appear as numIgnore in job stats rather than errors because the filter intentionally skips unwanted records without processing them, confirming the filter rules are working as designed.

When should I use script-based filters instead of expression rules in Celigo?

Use script-based filters in Celigo when your filtering logic requires multi-step conditions, date math, or custom evaluation that cannot be modeled by expression-based S-expression rules with standard operators like equals, contains, or logical combinators.