4 things you can do with Airtable and conversation design

Data is essential to creating contextual, dynamic conversations for users. Whether saving or retrieving information, conversation designers can utilize database tools like Airtable to customize any conversation on the Voiceflow canvas.

Here we look at the ins and outs of integrating with an Airtable base.

The API Step

The API step on the Voiceflow canvas can be a designer's best friend. Integrating with an Airtable base means the database tool is directly tied to a project's core steps and variables.

On the canvas, there are two popular API requests designers use with Airtable: GET and POST.

⬅️  GET Request retrieves data from a connected base. This API function accesses specific fields in an existing Airtable base and brings that information into the experience.

➡️  POST Request saves data to a connected base. Inversely, this API function takes user inputs from a conversational experience and records the information to fields in an existing Airtable base.

A look at the GET and POST request API steps on the Voiceflow canvas
A look at the GET and POST request API steps on the Voiceflow canvas
We've created two step-by-step video tutorials for using the Airtable GET and POST requests in Voiceflow.

Save these links to watch after reading:
⬅️  GET Request Tutorial
➡️  
POST Request Tutorial

What's Possible

Before you start adding the API step to the canvas, let's first consider what's possible. Utilizing the GET and POST requests, conversation designers unlock access to information outside of the canvas. Here are three additions to the CxD tool belt:

  • Pull or save information using an existing base - A conversation can now reference information in an existing database. This means that any data point that lives in the Airtable base can be referenced and pulled into the project. Similarly, data collected by the assistant can be saved to an integrated base.

    Here we're adding a list of tasks to a base for our assistant to access.
Here we're adding a list of tasks to our Airtable base for our assistant to access
Adding Task data to an Airtable base.
  • Map information to any variable in your design - Variables on the Voiceflow canvas allow for detailed, flexible conversational experiences. Now, Airtable data can be mapped to any variable in your project.

    Here's a glimpse at a designer mapping the "Task" field in Airtable to a created "recent_task" variable in Voiceflow.
Voiceflow's Integrations editor
Mapping Airtable fields to variables in Voiceflow.
  • Easily update and deliver content in realtime - Whether sending or receiving data, API requests happen in real-time. The assistant and Airtable base work in tandem, allowing designers to complement the existing conversation using a powerful database tool.

    Here the user asks the assistant for their next task, and the Airtable information is seamlessly pushed to the experience and delivered by the assistant. In this case, it's time to go grocery shopping.
Prototype experience of assistant pulling data from Airtable
Prototype experience of assistant pulling data from Airtable.
  • Create a single source of truth for scaling - Most importantly, Airtable is a solid segue into a content management system. As experiences get inherently more customized or scaleable, it's important to have a data system that scales with it. Using an external database of any kind is a great way to ensure your experience scales as your data does. Allowing your experience to pull and push data to a single source of truth, and make it easier for team members to add/remove data from your experience over time.

    This provides superior design and management flexibility over hard-coding responses or data directly into a project.

Use Cases

Using a database with your conversation designs inherently makes your experience more malleable. Using a tool like Airtable, custom variables can be pulled, tracked, and/or communicated across an experience. And although the to-do or task list is a foundational example in conversational AI, the use cases are endless.

Here are a few examples of how you can use Voiceflow and Airtable in your next project:

📚  Personal Tracker: A personal tracker relies on daily, consistent information that can be recorded and accessed later by the virtual assistant. How do you feel today? What was my mood last week Monday? An Airtable base integration makes this functionality a breeze.

📖  Consumer Product Catalogs: SKUs are constantly changing based on season, inventory, and trends. An Airtable base can be updated as needed, while the assistant will always have access to accurate product listings. Most of all, data integrity exists as there is one source of truth.

📝  Small Business Budgets: Manually entering data or searching through spreadsheets for information is a time sink for small business owners - not to mention a poor user experience. Deploying a budget assistant linked to an Airtable base can make it painless to record and check finances.

For conversation design teams, it's also important to note that adding the API step in the design and prototype stages can vastly improve developer hand-off. CxD teams are no longer reliant on developers to execute their API vision - and all the necessary code lives under the hood of the exported Voiceflow project file.

No matter the use case, deploying the API step is another way that conversation designers can rethink experiences across any channel. From IVR to web chat, an integrated Airtable database adds conversational depth and context for the user.

Ready to give these Airtable integrations a go? Start from scratch on the canvas or use this Mood Tracker template project that features an Airtable database GET and POST request.
We've created two step-by-step video tutorials for using the Airtable GET and POST requests in Voiceflow.
⬅️  GET Request Tutorial
➡️
 POST Request Tutorial
RECOMMENDED
square-image

RECOMMENDED RESOURCES
No items found.