Clip Node
Filter or clip geographic records against a boundary geometry
Last updated 8 Oct 2026
The Clip node restricts records to a geographic boundary. It can either filter records by whether their geometry falls inside (or outside) the boundary, or clip their geometries to the boundary using a PostGIS intersection/difference.
When to Use
Use Clip to restrict a dataset to a geographic boundary — a sales territory, a saved region, or a custom trade area — before downstream processing.
Configuration
| Field | Type | Description |
|---|---|---|
clipSource | region | draw | upstream | Where the boundary comes from (default: region) |
regionId | string | ID of a saved region (required for clipSource: region) |
drawnRegionId | string | ID of a region drawn on the map (required for clipSource: draw) |
upstreamColumn | string | Column holding the boundary geometry, read from the first input row (required for clipSource: upstream) |
geometryColumn | string | Column holding each record's geometry. If omitted, common names (geometry, geom, geojson, location) and lat/lng columns are auto-detected |
filterMode | boolean | If true, keep/drop whole records by spatial predicate; if false, trim geometries to the boundary (default: true) |
keepInside | boolean | In filter mode, keep records inside the boundary; in clip mode, intersect (true) vs. difference (false) (default: true) |
Example
Keep only records inside a saved sales territory:
clipSource: region
regionId: reg_emea_territory
filterMode: true
keepInside: true
Notes
- The boundary must be a
PolygonorMultiPolygon. - In filter mode (
filterMode: true), records that don't satisfy the predicate are dropped. - In clip mode (
filterMode: false), geometries are trimmed to the boundary; rows with no overlap are dropped. - Saved and drawn regions are resolved against the automation owner, so the region must belong to (or be shared with) the workspace running the automation.
Related articles
Still stuck? Browse the FAQ or contact us.