![airtable prosperworks zapier airtable prosperworks zapier](https://quizandsurveymaster.com/wp-content/uploads/edd/2019/12/Zapier-Integration-scaled.jpg)
The primary field for this new table could be anything, really, and I probably would have a formula field that showed the data of pet name, service name, and perhaps date. This would allow me to create a formula field that would give me the rate for that service based on the linked Pet record I'm assuming in the "Pets" table you have a field that denotes the size / weight of the dog or something? If so, I would put the different rates in "Services" as well, and then pull that data over into "Services Pets" via lookup fields, as well as the size/weight from the "Pets" table. Each record in this table would represent a single service for a single pet If I were you I'd have a standalone "Services" table that just listed all of the available services, and a fourth table called "Services Pets" or something, which would have a linked field to both "Services" and "Pets". When it comes to services however, since the services are occurring at the pet level.what's the primary field for the "services" table? Any other overarching guidance on what these tables could look like? I have "humans" and "pets" tables, which makes sense. I'm struggling to figure out what my tables should look like. Although Service A is always "Service A" for every pet, the price for Service A changes depending on the pet (for example, Service A will cost more for a heavier dog). A big part of my work is thinking about how I complete tasks by what services I need to do in any given day in other words, Spot might need Service A, Service B, and Service C done, and I care about knowing what services I've already done and what I still need to do for Spot. A pet will not come back for more services again in the future, so it makes sense that we could consider "pet" to be the main unit of analysis (sorry, I'm a social scientist by training, forgive my lingo). The projects themselves occur at the pet level, since one human might come back multiple times with different pets, and all the services for a pet occur at once.
![airtable prosperworks zapier airtable prosperworks zapier](http://software.kirknessassociates.com/blog_files/screen-shot-2017-10-07-at-13.39.55.png)
Each human can have multiple pets, and each pet can have multiple services. I have (a) the human client, (b) their pet, and (c) the services that they want for their pet. If you’d like to hire an expert Airtable consultant to help you with any of this, please feel free to contact me through my website: Airtable consulting - ScottWorldFor my small business, I have three levels of information I'm trying to manage.
![airtable prosperworks zapier airtable prosperworks zapier](https://on2air.com/uploads/How-to-Use-Zapier-Webhooks-in-Airtable.png)
There is a small learning curve with Make, which is why I created this basic navigation video to help. You can do the exact same thing that I mentioned above with Make, and you can also trigger it with a script instead of a button. I’ve written an entire post here about Make vs.
![airtable prosperworks zapier airtable prosperworks zapier](https://venngage-wordpress.s3.amazonaws.com/uploads/2021/07/Airtable-Zapier-integrations.png)
Make is infinitely more powerful & flexible & customizable than Zapier, and it is also significantly cheaper as well. However, I strongly recommend using Make instead of Zapier. (You can also add in extra parameters if you’d like, but those are unnecessary as well.) Just add the Record ID of the record as a parameter to the end of the webhook URL, and then have Zapier find the record based on its ID. Your button can just trigger the webhook URL on its own. You could use a script, but it’s unnecessary.