Sync is based on records shown in the View it is setup with. So if you add Filters to a view based on the conditions you're looking to use, I believe that could solve what you're looking for here.

Thank you, that did somewhat solve my problem. I was able to sync data with a specific condition to a separate base now.

I should have mentioned I am trying to be able to do this for various different conditions on the same view. That solution does not fully accomplish this because I would have to manually adjust filters and re sync.

For example, I want to have a main base with multiple views that has data for various clients pertaining to the view. This would be synced to an admin site, where they can sign in and manage their data. But then when they edit data, I would like it to sync their data to their specific base, which will then be synced to their personal site.

After looking further into it (Sorry, very new to Airtable), I realized that within a table I can have the main combined view and then also have a separate view within that table for each specific client, filter those appropriately, and then sync those client views to their appropriate base.

Setting it up that way should do the trick.

Thank you for the help!

Glad to hear that helped!!

Good thinking on exploring conditional syncs, this is one of those areas where Airtable’s architecture can feel limiting at first.

You’re absolutely right that Sync will always pull whatever’s visible in the source view, so your “separate filtered views per client” setup is the cleanest native approach
(https://support.airtable.com/docs/getting-started-with-airtable-sync)

If you ever need that process to scale or stay dynamic without manual filtering, you could pair it with automations or scripts that auto-adjust filters, duplicate filtered views, or even push records selectively via the API (https://airtable.com/developers/web/api/introduction)

That gives you more control over when and what gets synced, while keeping each client’s data isolated. For larger or multi-system setups, some teams move to event-driven two-way sync tools like Stacksync to handle those record-level sync conditions automatically, while keeping Airtable as the main interface.