Daniel K. thanks for the response. we built the function and went to run it on historical rows. Instead of just running that cell it did the whole row and re-ran already enriched contacts which drained the credit. It seems like it wont be an issue moving forward because its set to auto run on new records.
If I am understanding you correctly, the request needs to trigger before or at the same time as the enrichment to avoid re-running?
Thanks for the tip on auto dedupe -that is helpful.
High level: trying to get the lay of the land so we implement properly and economically efficient on credits.
The function checks if the contact is already in our redshift database as a customer or active prospect. We want to ensure the rep reaching out to the new contacts in the clay table doesn't work existing deals or leads from other reps in our DB.
The rep is currently working out of clay for prototyping the motion for this project and then will move to CRM.