The Zap creates multiple records for new leads with the same phone number when importing.

Thanks @Troy Tessalone  :) 

This makes sense, but I still get duplicate values: 

This is my config: 

Is it correct? 

Thanks so much for helping!

@ssielmann 

That isn’t a valid phone number value, which may be contributing to the issue.

You’re right @Troy Tessalone  , the test value is wrong. But the live data is correct! Thanks for checking, great idea. 

Any other hint by any chance? Can’t believe it’s not working.

@ssielmann 

We would need to see screenshots from the live Zap Runs to see the DATA IN/OUT for each Zap step.

https://zapier.com/app/history/

Sure thing 🤓

Complete list of data in:

• table_id:

  01HAM9F50HEC25EXCPH1VPQ7TW

  filter_count:

  1

  field_data_key:

  data__f9

  operator:

  exact

  lookup_value:

  xxxxxxxxxx

  new__data__f1:

  {{205916918__fields__User First Name}}

  new__data__f2:

  {{205916918__fields__User Last Name}}

  new__data__f5:

  {{205916918__fields__User E-Mail}}

  new__data__f7:

  {{205916918__fields__User E-Mail}}

  new__data__f8:

  2023-09-27T21:34:30.816Z

  new__data__f9:

  491456543786

  new__data__f10:

  {{205916918__fields__ref}}

  new__data__f11:

  {{205916918__fields__aff}}

  new__data__f16:

  {{205916918__fields__User Street & No}}

  new__data__f17:

  {{205916918__fields__User ZIP}}

  new__data__f18:

  {{205916918__fields__User City}}

  new__data__f19:

  Ja

  new__data__f20:

  {{205916918__fields__Mandate City}}

  new__data__f21:

  golilo

  new__data__f27:

  {{205916918__fields__Unterschrift - Signature}}

  new__data__f26:

  {{205916918__fields__Mandate Date}}

  new__data__f28:

  {{205916918__fields__Unterschrift}}

  new__data__f38:

  Aboalarm

  new__data__f29:

  {{205916918__fields__Bitte nenne uns den Link zu deinem Facebook-Profil}}

  new__data__f30:

  {{205916918__fields__Nutzt du dein Facebook-Profil auch beruflich?}}

  new__data__f31:

  {{205916918__fields__Bist du vor oder nach dem 25. Mai 2018 Facebook beigetreten?}}

  new__data__f33:

  {{205916918__fields__Beschreibe, welche Art von Werbung du erhalten hast:}}

  new__data__f34:

  {{205916918__fields__War die erhöhte Belästigung vielleicht sogar ein Grund dafür, dass du deine Handynummer gewechselt hast?}}

  new__data__f32:

  {{205916918__fields__id-b190d980}}

  new__data__f35:

  {{205916918__fields__Ich werde meine Einstellungen zur Privatsphäre ändern}}

  new__data__f36:

  {{205916918__fields__Ich werde Daten von meinem Facebook-Profil löschen}}

  new__data__f37:

  {{205916918__fields__Ich werde mein Facebook-Profil löschen:}}

  new__data__f39:

  Ja

  zap_id:

  205916918

  zap_step_id:

  208478537

And data out: 

• new:

  data:f1:

  null

  f2:

  null

  f3:

  null

  f4:

  null

  f5:

  null

  f6:

  null

  f7:

  null

  f8:

  2023-09-27T21:34:30Z

  f9:

  491456543786

  f10:

  null

  f11:

  null

  f13:

  null

  f14:

  null

  f15:

  null

  f16:

  null

  f17:

  null

  f18:

  null

  f19:

  Ja

  f20:

  null

  f21:

  golilo

  f22:

  null

  f23:

  null

  f24:

  null

  f26:

  null

  f27:

  null

  f28:

  null

  f29:

  null

  f30:

  null

  f31:

  null

  f32:

  null

  f33:

  null

  f34:

  null

  f35:

  null

  f36:

  null

  f37:

  null

  f38:

  Aboalarm

  f39:

  Ja

  id:

  01HBC91BBMJZVRWD6RVDK36GTJ

  edited_at:

  2023-09-27T21:34:34.866546+00:00

  created_at:

  2023-09-27T21:34:34.868000+00:00

  schema_revision_id:

  72

  errors:

  record_id:

  01HBC91BBMJZVRWD6RVDK36GTJ

  table_id:

  01HAM9F50HEC25EXCPH1VPQ7TW

  change_id:

  01HBC91BBV9YJTKQBJ1ZS71NAD

  _zap_data_was_found:

  false

  Fields with no value:

  old

I just saw, that an extra “49” was appended to the phone number. This can be an issue, but not the ultimate one, because the zap also does not update this appended version of it the next time I run it. 

@ssielmann

Did you update this value to be the output from the Formatter step?

Yes :) 

The crazy thing is - it all used to work a couple of hours ago :/ 

@ssielmann 

You can try submitting a ticket to the Zapier Tables team to see if perhaps some recent update broke this Zap action: https://eap.zapier.app

Thanks, will do!

@Troy Tessalone I had another idea and created a text field for the matching (instead of using the phone field, which has its own rules). 

No there are no duplicates, but the information does not appear anywhere in the table. 

It was all successful and didn’t give any errors, do you have any idea why this could happen?

@ssielmann 

FYI: Step 4 logic is really a find else create record

You’ll need to check the DATA OUT

That should include the Record ID.

Yes, the record IDs are the same, so that matching should happen in theory. 

I can even find the values when testing: 

It appers in the logs: 

...but somehow disappears along the way: 

It’s really lost: 

vs

@ssielmann 

If Zapier Tables isn’t working for you try using Airtable.