Source filters

Source filters are the per-source settings that decide exactly which records, files, or channels a connector pulls into the context repository.

Category

Product feature

See all terms

What are source filters?

Source filters are the settings a workspace applies to a connected source to control what data syncs in. Instead of ingesting an entire account, a workspace narrows the scope using options tied to that specific tool: an object type, a list, a folder, a channel, or a time range. Native connectors surface these filters at setup and each connector exposes its own set based on what that tool supports.

Why do source filters exist?

A connected account almost always holds more than a workspace needs in its context repository. Pulling all of it in wastes sync time and resources, and buries the records that matter under ones that don't. Source filters exist so a workspace imports only the data it needs, narrowing ingestion down to the contacts, files, or channels relevant to the company. More frequent syncs keep the repository current but use more resources, so narrowing scope up front also keeps ongoing syncs lighter.

How do source filters work?

Each connector defines filters around what its data model supports. Specific information on filter settings and available filters can be found in the docs. Whatever a connector's filters allow, they determine what actually transfers into the context repository, and each source's own sync logs show what synced against what the filters allowed.

FAQ

Do source filters work the same way across every connector?

Why does Slack filtering include a time range?

Do narrower source filters make syncs faster?

What happens to files a Google Drive filter doesn't cover, like oversized files?

Where do I set filters for a connected source?

Make your company AI-native.