I’m trying to ingest a new user registration (password’s being handled separately).
I want to make sure that the new registration does not use an email address already in the DB (prevent duplicate accounts–ideally even if they’re using “+variable” in something like a gmail address).
I’m currently using automations, but I can’t seem to get around the “Find Records Action 0 results stops the automation” flow. I actually want to update the record AFTER a Find Records determines there aren’t any duplicates.
I’m not using scripting – “Plus” account level and coming in from the #nocode crowd.
Here’s the where I am thus far:
WHEN: a record is created in Ingest Users Table
ACTIONS: Find Records in Active Users Table where email = [new record email] Update Record (that was created) → set Duplicate = true
[I would IDEALLY be able to handle Find Records = 0 results with an Update Records → set Unique = true, then have a When Record Enters View that copies the Ingest User record to the Active Users Table.
WHEN: a record enters a view (Ingest Users.Unique = true)
ACTIONS: Create Record in Active Users Table Update Record (that entered view) in Ingest Users Table → set Processed = true Find Records in Active Users Table where Created From = [record that entered view] Gmail send welcome email
[again, IDEALLY handle Find Records in Active Users Table = 0 results with error logging/graceful failure involving logging and emails]
I have a number of different jukes using multiple different table views qualified by different checkbox variables (and a few formulas). Those fail because somehow the when enters view triggers can fire WHILE another automation is running. So if I, say, mark a record as Unique = true, then check for duplicates, then update → Duplicate = true AND Unique = false, the record already popped into the IF Unique = true view and triggered the next automation.