Typeform => Airtable without duplicates

Topic Labels: Extensions
2810 5
Showing results for 
Search instead for 
Did you mean: 
5 - Automation Enthusiast
5 - Automation Enthusiast


I use airtable for a recruitment activity. I already have a candidates database in airtable. I want to give the possibility to futures candidates to come on the database and be recorded in airtable. I already connected my typeform to the airtable (in a basic way, proposed by typeform). It works.

When I fill the typeform, it creates a new line in the database on airtable, this is ok.
But if the candidate already exist in the database, I would like to avoid the duplicates. I would like that airtable recognize that the candidate is already in the airtable database and not create a new line but update the existing information concerning this candidate.

I was told that Zapier could solve this problem. I tried to do it through Zapier. I don’t know how to use the part “customize record”.

Thank you for your help,

5 Replies 5
6 - Interface Innovator
6 - Interface Innovator

Hello Alexis,

I can suggest you a way to do it without Zapier. Assuming what you’re looking for in the first place is to avoid duplications, not necessarily to build an automation.

  1. Create a first table Candidates that will list your candidates (1 record per candidate). I suggest you use Email address as primary key.
  2. Create a second table Submitted forms that will list all the submitted forms (1 record per candidate). Use a simple Autonumber field as primary key.
  3. On the Submitted forms table, create a Link to another record field to the Candidate table. But don’t display it on the form.
  4. Create your public form on the Submitted forms table (or connect your typeform to it). Make sure to add an Email field on your form to collect candidate email address. But don’t display the Link to another record field to candidate on your form.

Then, each new filled form will create a record in the Submitted form table.

All what’s left to do is to link manually the submitted forms to their related candidates, assuming we identify them by their email address. Might be enough for you in your case to do it once a day, as I assume you don’t need your base to be synch systematically for each new submitted form (in that case you would need Zapier indeed).

The good news is, as you can see in the Gif below, You can do that in 2 clicks by simply copy pasting in the Submitted forms table the whole Email column in to the Linked Record column.

Note the submitted forms records 3 and 4 came from the same contact. As a result, both forms were linked to the contact number 3.

With the right structure in place, Airtable is able to handle duplicates for you :

  • If the Email (primary key) does not exist in the Contact table, Airtable will create a new record (contact record 4).

  • But if the Email already exists, Airtable won’t create a new record, but will link the submitted forms to the existing contact.



Thank you very much for your help. I am going to try your solution.

Thank you,

Le lun. 10 févr. 2020 à 04:46, Noamsay via Airtable Community Forum a écrit :

5 - Automation Enthusiast
5 - Automation Enthusiast

Hi @Noamsay

I have a similar problem, which I explain in a post I recently created,

if you can review it and give me some recommendations, please


Hi @faiberts
Thanks for reaching out !
Your question is about a specific error when integrating typeform via Integromat, and I’m totally unfamiliar with both, sorry. If in the future you have a question related to the design of the base (like the original problem raised) don’t hesitate to tag me.

10 - Mercury
10 - Mercury

This problem can be solved using this extension. It does exactly what you want. If a candidate is new, they’ll get the registration form. If they are already registered, they’ll get a form to update their existing record.