How can I ensure that my table contains no duplicates?

Here’s the automation I’ve set up.

  1. I search for all responses in SurveyMonkey and send the response IDs to a sheet.
  2. I take the IDs from the sheet in SurveyMonkey so that it gives me all the contact details corresponding to the ID (the response).
  3. I send all this to a other table.

I have to do it this way because I can’t collect respondent information directly with SurveyMonkey.

My question :
Each time I run MAKE, I receive all the responses in my table. BUT I would like to receive only NEW responses. So I thought I’d filter to say that “if I already have the answer, don’t include it in my table”.

At the moment I can’t do this filter. Do you have a solution?

Thanks for your help,

Hi @Chantepie,

Any reason not to use New Response Event instead of Search for a Response? You can replace the first Search for a Response with New Response Event which will trigger the scenario Immediately whenever there is a new form submission.

1 Like


Yes, if I call New Response Event I don’t get the information I want.

Information with New Response Event :

Information with my technique:

Then I would change your scenario and have it start with the “New Response Event” at the beginning of the scenario followed by a “Get a Response” module which gets all the data from new responses. That way you can have the right trigger (new responses) but see all the data.

1 Like

Even if it works, it doesn’t solve my problem, does it?

If I understood your problem correctly it is that you get double entries because you always ask for all responses. If it is only new responses that you are interested in, the approach I described would be a lot cleaner and wouldn’t generate double entries.
Or am I misunderstanding you somewhere?

1 Like

What you are probably looking for is something like and “update” module instead of an “add” module at the end. I have a lot of scenarios that do something similar to:

  1. get data from one place,
  2. check if it already exists in the other place,
  3. if yes then update that record, if no, then create new record.

Is that what you mean? That can be achieved quite easily.

1 Like

Yes, that’s exactly what I need.

Here is a sketch of how that would look like. There are ways to do it which might require less operations but this method is reliant and easy to understand, I hope.

1 Like

Thank you very much, it works well