With Zapier, you can connect Airtable to thousands of your other go-to apps to take your automations to a whole new level. Instead of manually creating the same record, you can use record templates to quickly populate a fully fleshed-out base for each new project.Īirtable Automations give you a taste of simple, hands-free data management. Let's say you use Airtable to manage projects that often involve the same set of tasks and milestones. Record templates allow you to build templates for your most repeated records. It's a useful way to get others to do things like approve requests or provide status updates-without getting bogged down by other details. Airtable's Interface Designer lets you create custom dashboards containing only information you want collaborators to see. Sure, you can filter the data using different views, but even combing through different views can be a dizzying task. If your base contains a lot of data, it can be overwhelming for other collaborators to navigate. You can get insights on everything from how to fix a broken Airtable automation to high-level data on user activity. For example, with a chart extension, you can visualize your data as a bar, line, or donut graph directly from your base.Īirtable insights help teams understand how everyone is interacting with their shared bases, and suggest ways they can optimize them. For example, you can build a workflow to automatically notify your team in Slack when the project status on an Airtable record changes to "complete."Īirtable Extensions let you add extra functionality to your bases. Click on a feature for an in-depth guide on how to use it.Īirtable Automations enable you to create up to 50 automated workflows directly within an Airtable base. Note: This provides a high-level overview of each feature. Once you've created a few bases and you're comfortable navigating your way around Airtable, use these advanced Airtable features to get even more out of your database. If this isn't how you want to visualize your data, create a new view. 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.By default, Airtable will populate your data into a grid view. Doesn't really matter unless you need it to be in a specific format for linking to another table or you have users filling out forms and such 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. 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. For my small business, I have three levels of information I'm trying to manage.