Optimizing API Calls in Enrichment Tables to Reduce Credit Usage

Gabe N. · 2024-10-06 15:17:03.531488+00

im running an http call out of a cell to our data warehouse that returns a value. It is consuming a massive amount of credits to do when I batch run against existing rows. This cell is in an enrichment table so my hunch is it is re-running the email and phone waterfalls when I trigger the api call but i'm not sure.

Optimizing API Calls in Enrichment Tables to Reduce Credit Usage | Clay

8 comments

· Sorted by Oldest

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Gabe N.
·
·
https://app.clay.com/workspaces/290057/tables/t_aibz85cVB8aj/views/gv_66dFSyzC2MKr
Daniel K.
·
·
Hi Gabe! So, if I understand correctly, you're looking to avoid enriching leads that are already in your CRM/database, right? To tackle this, I recommend kicking things off with an HTTP GET call to verify if the leads are already in your system. If they're not, go ahead with the enrichment process and then proceed to use HTTP POST to push them to your CRM/database. Another helpful tip is to turn on auto-dedupe on your RB2B table (e.g. Linkedin URLs). This will help prevent starting workflows with leads that have already visited your website. Also, I'd suggest arranging the Phone waterfall enrichment with providers from the lowest to the highest credit costs. This way, you can optimize your usage and make the most out of your credits. If you need any more guidance or have further questions, feel free to reach out! 😊
Gabe N.
·
·
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.
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
LuisArturo
·
·
Hey there Gabe thanks for reaching out,, jumping in for Daniel here, yes to confirm for Daniel, you will need the request to trigger before the enrichment runs.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Gabe N.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Gabe N.
·
·
https://app.clay.com/workspaces/290057/tables/t_aibz85cVB8aj/views/gv_66dFSyzC2MKr
Daniel K.
·
·
Hi Gabe! So, if I understand correctly, you're looking to avoid enriching leads that are already in your CRM/database, right? To tackle this, I recommend kicking things off with an HTTP GET call to verify if the leads are already in your system. If they're not, go ahead with the enrichment process and then proceed to use HTTP POST to push them to your CRM/database. Another helpful tip is to turn on auto-dedupe on your RB2B table (e.g. Linkedin URLs). This will help prevent starting workflows with leads that have already visited your website. Also, I'd suggest arranging the Phone waterfall enrichment with providers from the lowest to the highest credit costs. This way, you can optimize your usage and make the most out of your credits. If you need any more guidance or have further questions, feel free to reach out! 😊
Gabe N.
·
·
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.
Channeled
APP
·
·
Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.
LuisArturo
·
·
Hey there Gabe thanks for reaching out,, jumping in for Daniel here, yes to confirm for Daniel, you will need the request to trigger before the enrichment runs.
Channeled
APP
·
·
We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!
Channeled
APP
·
·
Hi Gabe N.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: