Enriching Website Leads in Real-Time with Clay API After Form Submission | Clay

Enriching Website Leads in Real-Time with Clay API After Form Submission

Can we enrich website visitor through clay API near real time after they submit a form? We used to use Clearbit to do this and after the industry is enriched we can route leads. If we need to first import leads into clay app and then trigger the enrichment, it is not real time so that we cannot immediately route the lead, which can cause a problem.

14 comments

Mark L.
·
·
Jinghang, have you considered using webhooks? A webhook allows you to stream data into Clay without having to manually import/refresh new records every time they are created. Depending on your form setup, you could potentially forward the data to a Clay webhook at time of submission. And from there, Clay could run the enrichments as each new row is created. Here are a few resources for webhook imports: * https://docs.clay.com/en/articles/9730014-import-data-to-clay-using-webhooks * Video showing a few automations you can set up in Clay (webhook example in the first few minutes of this video): https://youtu.be/yw5paDolwTQ?feature=shared Feel free to take a shot at building your first webhook table and let me know how it goes! ✨😊
Jinghang H.
·
·
I am aware of the webhook. The problem is not about how to import lead into clay through API. It is about we need the enrichment at website. For example, an api call with email as request payload that returns the enriched info like industry so that at website we could add this industry field into form submission or lead router (we use revenue hero to do router based on form submission).
Daniel K.
·
·
Hi Jinghang! Clay does not currently offer external API endpoints for enrichment or other actions outside of the main user interface. This has been raised a few times, though! However, you can still integrate with Clay using Webhooks to auto-import records into a workflow and then use HTTP API integrations to push it to your custom API. If it helps, we can also do the routing within Clay!
Brice D.
·
·
Jinghang H. One solution is to push your lead into Clay, run the enrichment, then push your lead out the other side of the table to a Zapier webhook and have Zapier update the record in your CRM/MAP/CDP, then have downstream routing trigger on that update. Another approach we use is a 3rd party API that supports webhooks, where you push in the company domain and you get back a data record, much like you see here in Clay columns that speak to data providers. Either approach would work. The second approach obviously requires a paid relationship with a data provider.
Brice D.
·
·
One problem with all the approaches is a lack of consistency in the industry taxonomies. And even when you have a formal taxonomy like SIC or NAICS, the lack of consistency in how the values are assigned. I find that you end up doing some mappings and guess work to put companies into the right industry buckets, for your specific organization’s taxonomy. The need for this mapping argues for my first approach, where you are doing the mapping / guessing in a Clay table, then once you’ve made a decision, you push the mapping out to your master data system via Zapier or some similar middleware routing.
Channeled
APP
·
·
Hi Jinghang H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Jinghang H.
·
·
Thanks, everyone. Regarding Clay HTTP API call, can we setup rate limit? The endpoint to be called might have rate limit.
Daniela D.
·
·
Hey Jinghang! Thanks for reaching out. Happy to help. The HTTP API feature has an option to set a custom rate limit. However, the request limit set must average at least 5 requests per second. Sharing an additional guide for HTTP API: https://docs.clay.com/en/articles/9672489-http-api-with-clay Let me know if this helps! https://downloads.intercomcdn.com/i/o/w28k1kwz/1215425560/cd94f5ef57ce509772212fb1c9c7/CleanShot+2024-10-14+at+16_26_23%402x.png?expires=1728921600&signature=f2345453020c58b767967fdf3fa3f04f1c5e822688cb3893f006138b3dc7cda4&req=dSImE818mIRZWfMW1HO4zZ0l%2BxnkwTt1FHXE0Kkw0YqmDxoU48OE%2FLviBxI3%0AqAYl%0A
Jinghang H.
·
·
Sorry I am still a bit confused, by at least 5 requests per second, you mean exceeding 5 requests per second? For example, 10 requests per second but not 1 request per second?
Daniela D.
·
·
Hey Jinghang! Sorry for the confusion. Happy to help✨. To clarify, the minimum rate limit allowed when running the HTTP API integration is 5 requests per second. You can set it as this range or at a higher limit, but not below. Does your endpoint have a lower rate limit?
Jinghang H.
·
·
The rate limit is 50 requests / 10 seconds, so I am thinking to set a lower number. If it is not possible, it’s ok
Daniela D.
·
·
Thanks for the reply! In this case, you can set a limit as low as 5 requests per second with the custom setting in the HTTP API column. Let me know if this helps.
Channeled
APP
·
·
Hi Jinghang H.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: