Airtable Beginner's Guide Part 2: Filters and Views, Automation, and Interfaces

Continue learning the basics of Airtable with XRay.Tech as we explore linked records, filters and views, workflow automation, custom interfaces and more.
Check out Airtable, Zapier, Softr, and other software in this XRay Workflow resources board:
www.xrayworkflow.com/resource...
---
00:00 - Intro
00:41 - Linked records
02:14 - Add lookups to linked records
03:07 - Linked records vs select fields
04:05 - Add a filter to your table
05:58 - View types in Airtable
09:26 - Automations in Airtable
10:14 - Build an automation in Airtable
13:23 - Using filters and views to trigger automations
14:23 - Third-party automation providers
15:25 - Airtable interfaces
16:07 - Build an interface
---
To learn more about how you can use automation and other techniques to improve your company's workflows, visit our website:
xray.tech
Read our blog posts for tutorials and deep dives into automation: xray.tech/blog
Check out our Zapier Experts page for reviews and more information about XRay: zapier.com/experts/xray-tech/

[@salarmh4193]

very well described tutorial ... good job

[@XRayAutomation]

Thanks! We appreciate the comment!
Checkout our most recent Softr beginners guide if you want build public apps on top of Airtable

[@colleenkennedy4505]

Excellent, tutorial. Thanks! I have 2 questions, if I may.
1. Is it best practice to name the linked field something different than the name of the original field? Why or why not?
2. After creating a linked field with a look-up should I hide the look-up field til I need it so the table doesn't become too cluttered?

[@XRayAutomation]

Thank you & great questions!
1. Generally, we leave the name blank when creating a field- that way the field is auto-named consistently, this is true for linked record fields too. Also, for formula fields, we always preface with a “fx” that way on zapier you know that it’s a formula field and don’t try to map variables to it.
2. Great call out! We normally create a section of views called “by field type” - then have views for only linked record fields, linked + lookup fields, only formula fields, and key fields to that specific table.
Using sections to group things, like ⚡️Automated Views - really helps to keep things organized.
Also, make interfaces instead of views to actually do workflows. Giving everyone edit access to the data just gets messy