Using a Conditional Form with Airtable (Part 1)

There are two common ways to get data into a database. You can either:

1. Import a dataset in bulk
2. Bring in data one with each new record submitted

For the most part, I recommend the first option, bulk imports, only when first setting up a database. Ideally, once the base is established, it makes the most sense to bring new records in automatically (saving you the need to import data over and over again).

To automate the creation of records, we have a few options. The most commonly used process is to have data entered into a form, which is then automatically brought into our database through some IFTTT (if this, then that) logic. Specifically, (1) when form is submitted by outside user, then post the relevant data to our database.

The real trouble comes in when the form can vary, based on the answers within the form. We call this conditional logic, and it's available in most form softwares (Jotform and TypeForm included).

But, you might ask, why would we build a form outside of Airtable - doesn't Airtable also have forms inside their software?

And you'd be totally right to wonder that! But, as of the time of this writing, Airtable does not offer conditional logic in their forms. For this, my friends, we're going to need to create a form in a third-party software, and then bring the responses to that form into our Airtable database with an automated process.

If you've ever wondered about the true power of conditional forms, be sure to explore this week's video - where I outline a real use case, build it in Jotform, and integrate responses with an Airtable database.

And... if you liked this video... check back next week for the conclusion that will use automation 'pathing' to create different automation outcomes!