SKILL.md
Configuring Filters
A filter is a record gate that decides which records pass a point in the pipeline. What happens to the rest depends on where it sits: an export's filter silently drops them from the flow, while a lookup's or an import's filter only skips that step for them. Filters are configured directly on exports, imports, and flow router branches -- not as standalone resources.
Concerns when configuring a filter:
- Placement -- where in the pipeline the filter runs (output filter on export, input filter on lookup, pre-import filter, branch routing condition)
- Mechanism -- expression-based rules (declarative, no code) vs. script-based (full JavaScript control)
- Expression syntax -- prefix-notation S-expressions with operators, field access (
extract), type coercions, and logical combinators (and/or/not) - Settings references -- dynamic filter values pulled from flow, export, import, or integration settings via
settingsaccessor - Script alternative -- when expression rules cannot handle the logic (loops, multi-step conditionals, external lookups), use a filter script instead. Dates relative to now and arithmetic across fields don't need one (Dates and Computed Values)
Four Places Filters Appear
Output filter (export filter)
Applied after records are retrieved from the source system. Records that match continue through the flow; records that do not match are silently dropped. Available on all export types.