Looking to generate leads for your business, or qualify them after you’ve received their email from a service like Typeform? This tutorial is for you! We’re going to be using Typeform as a lead intake form and then use Standard Library to both connect to the Clearbit API to qualify those leads and store the updated lead information in AirTable.

To do this, we’ll be using Standard Library’s simple API-centric cloud platform and the online editor for APIs, Code on Standard Library— if you’re not familiar with APIs yet, don’t fret! All we mean is you’ll be writing a little bit of your own custom business logic.

Marketers, CSMs, Sales Executives, this one’s for you! 😉

What You’ll Need Beforehand

1x Typeform free account — A platform for building dynamic online forms including landing pages, polls, quizzes and more.

1x Clearbit free account — Clearbit’s Enrichment API takes an e-mail and returns a person’s employment, title, website, Linkedin and more.

1x Airtable free account — AirTable is a combination of a spreadsheet & database.

1x Standard Library free account — A Platform for building and deploying APIs, linking software tools, powering Slack apps, automating tasks, and more.

5x minutes (300x seconds) of your time — These tools, used together, will save you hours of work!

How it Works 🤓

When a lead submits his/her e-mail via your embedded Typeform, a webhook will trigger an API you’ve built on Standard Library that sends a notification via HTTP POST request. The request body (containing the response data from Clearbit’s Enrichment API) will be sent in JSON format to populate your Airtable base.

So let’s get to it!

Minute 1: Fire Up Code on Standard Library From your Browser

We will link Typeform, Clearbit, and Airtable via Code on Standard Library the online API editor built by the team at Standard Library. You’ll be deploying your function to Standard Library with zero setup or installation on your local machine.

Once you’ve logged in to Code on Standard Library click on the “Community API Sources.”

Find and select “typeform-clearbit-airtable by @JanethL.”

Make sure to give your API a unique name, for example:

Once loaded, you will be taken to the __main__.js located under the functions directory (folder). This is the code that will connect your Typeform to Clearbit’s Enrichment API and to Airtable. Once it is deployed live onto Standard Library, an https url endpoint is generated. You’ll need the endpoint to set your webhook on Typeform. But let’s not get too far ahead — first, we need to finish setting up your Standard Library API with your unique Clearbit and Airtable keys.

Example Code by Steve Meyer, You Should See Something Like This!

Open up the env.json file. You’ll see three different variables:

Let’s start by finding your Clearbit API key.

Minute 2: Copy and Paste Your Clearbit API Key

First you’ll want to log in, or sign up for a free Clearbit account at https://clearbit.com/.

Once signed into your Clearbit’s dashboard, navigate to the API Key tab and copy the first key — the secret API key.

Note that below your keys, Clearbit has suppression settings to exclude certain contacts from your enrichment project to satisfy (GDPR).

Now return to Code on Standard Library and populate the “CLEARBIT_API_KEY”: variables inside env.json. We now have two remaining variables to populate.

Minute 3: Find Your API Keys on Airtable

Once you’ve logged in or signed up for Airtable, select the account icon on the top right corner to see your account information. Click generate API key and copy and paste that key into “AIRTABLE_API_KEY”: “”, inside your env.json file.

Now, for the last variable, click the link below and once routed to my Airtable Base sample, select Copy base on the upper right corner. It’s your base now!

Once you’ve added a copy of my base onto your workspace, enter your “LeadGenerator” base. On the upper right corner click Help and then select API documentation.

Find and select your Airtable base key as I have done in the screenshot:

After you’ve copied and pasted your Base’s key into your env.json, your env.json file should look like this: