Skip to main content
Question

Syncing more than 20 sources into one table

  • June 27, 2025
  • 2 replies
  • 103 views
C
Forum|alt.badge.img+1

In my setup, each of my clients has their own base and interface. They can submit support tickets through their interface, and those tickets feed into a synced table in my team base. I just got my 21st client and it says I cannot add any more sync sources to my support ticket table.

I have the support tickets going to a second support ticket table right now, but our support team doesn’t get them in their support ticket feed. I thought maybe I could create an automation that copies the support tickets from the second table into the original support ticket table, but that won’t work because I can’t create an automation to create a record in a table synced to another source. 

I thought about creating a new base just for support tickets and then syncing that back to my Team Base, but then my team can’t edit the records once they get to the team base. 

 

Is there another way to create a table that syncs all of my clients’ support tickets into one table in my team base that my team can edit?

    2 replies

    ScottWorld
    Forum|alt.badge.img+35
    • ScottWorld
    • Genius
    • June 27, 2025

    ​@caseycan 

    That is actually not the best way to setup your database system.

    Ideally, all of your clients and support tickets should be unified together in ONE master base with only ONE unified interface (instead of 20 bases and 20 interfaces).

    Then, you don’t need to keep replicating all of your work across multiple bases. And you don’t need to worry about the limitations of sync tables.

    Whenever a client logs into your one unified interface, you would show them only their own support tickets. You wouldn’t show them any of the other clients’ support tickets.

    However, if you want to keep your existing setup (which I would not recommend), and you want your team to be able to edit support tickets that live in a non-editable sync table, you can take one of the following approaches:

    1. Give them a button to jump to that record in the support ticket base.
    2. Upgrade to a Business or Enterprise plan, which gives you the ability to edit records in the sync table.
    3. Use Fillout’s advanced forms for Airtable, which is 100% free and allows you to update Airtable records through a form. Fillout also offers hundreds of other advanced form features that you can’t get with Airtable’s native forms. You can see how to setup an “update record form” in my video below, which also shows off many other advanced techniques using Fillout: Using Fillout to create an eSignature approval process with PDF file creation.

    Hope this helps!

    If you have a budget and you’d like to hire the best Airtable consultant to help you improve your system, please feel free to contact me through my website: Airtable consultant — ScottWorld

    TheTimeSavingCo
    Forum|alt.badge.img+31

    Hmm, so to confirm, what you've got now is:

    21 Client bases

    1 Team base

    And you want all the data from the 21 Client bases to show up in the Team base as editable records, and so changes in the Team base will reflect in the Client base?

    If so, I don’t think so I’m afraid.  If it was purely display then syncing the 21 client bases to 2 “Consolidate” bases and syncing those would work, but then you wouldn’t be able to do two way editing

    I can think of a workaround to do with using scripting to make edits for you etc after doing the consolidated base thing above, but it’d involve a fair amount of set up and workflow changes for your team, would be fragile, and would need to be extended whenever you a new client came onboard

    At this point it’s probably less work to just bite the bullet and restructure everything into a single base instead as that’d solve your problems pretty neatly (unless you’re hitting the 100k record limit when you consolidate everything like that which….yeah I hope you’re not facing that)

    Adam, Airtable Consultant - thetimesaving.company
    MatteoCrOps
    Terms & ConditionsAccessibility statement