I’m setting up my landscape company in Airtable and one major aspect is scheduling subcontractors and collecting data from them in the field. I have a central Base in my Pro workspace that is handling everything from job intake to billing. I want my crews in the field to be able to use the Airtable app to get their daily assigned projects and enter data about what they do that can be used to calculate payroll and billing info. A popular topic around here is the lack of granular sharing permissions and this is something I’m trying to do a workaround for. While data security is a concern, I also don’t want to pay for a license for every crew to use the Pro workspace base and I think that the simplicity of having their own base with only their schedule in it would be a lot easier for them to use. It also gives them a history of what they have done so they can make sure they get paid accordingly and they don’t see what the other subs are doing.
Idea: Create free bases for each subcontractor or each crew in a separate workspace. Create a Zap with logic that will send job instructions along with the original record ID to the subs’ bases from the main base when they are assigned a job. When a job is filled out and clicked as complete in the free base it would trigger a Zap that would update the main base (using the original record ID) with the job data.
**Question:**If I had to create up to 15 auxiliary bases would this web of Zaps be reliable enough or is this just asking for missing data and tracking down failed connections? The update Zaps would run throughout the day and probably not at the same time. The assignment Zaps would run at the same time, maybe as many as 15 at a time(10 fields of data).
I’m moving from smartsheet where I got burned trying to rely on Azuqua to transfer data between sheets so I’m nervous to move forward with what feels like an elaborate workaround that depends on Zapier.