Hi, I need some help in connecting my Lusha and zoominfo account with clay and use it for phone number and email enrichment along with clay. But since there is no direct API integration for these platform can someone help me how to connect these two platform with clay?
💤 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!
Hi Dakshin! Unfortunately, the Lusha team has requested that we remove their integration from Clay. We understand how valuable this feature can be for you. We encourage you to reach out to Lusha directly and express your interest in having the integration reinstated. You can contact them at this link. In the meantime, you can use the HTTP API with your API key. This works also with your Zoominfo account. If you have any other questions or need further assistance, please let us know.
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!
Hi Dakshin K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Can i get a video on how to do this?
Hey Dakshin, Thanks for reaching out! Here's a video walking through HTTP API JWT set up (needed for Zoominfo): https://www.loom.com/share/620a30bc74614e13925b0c05922fd5a9 Additional details for set up: Location of JWT token in Auth Response: jwt Auth header: Authorization Method: POST Endpoint for company: https://api.zoominfo.com/enrich/company Endpoint for contact: https://api.zoominfo.com/enrich/contact Lusha (set up with HTTP API, not the JWT option): This is the endpoint needed to enrich contacts : "https://api.lusha.com/person?firstName={{inputname}}&lastName={{inputname}}&company={{inputname} Post method: GET Example body input: { “firstName”: :firstName, “lastName”: :lastName, “organizations”: [ { “company”: :company1, “domain”: :domain1, “isCurrent“: true }, { “company”: :company2, “domain”: :domain2, “isCurrent“: false } ] } Header Name: Authorization Header Value: YOUR_API_KEY Quick video on how HTTP API works: https://www.loom.com/share/114ff06973bd4ed7985b32fa031be867 Docs: https://docs.clay.com/en/articles/9672489-http-api-with-clay Bonus! troubleshooting example of failed body parse issues: https://www.loom.com/share/678e4c40e8c14894a6cd53948176e434 Let me know if this helps.
Hi Dakshin K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Hi there - this is such a good start, but I feel like I need more as someone without a background in JSON web tokens. For the Location of JWT token in Auth Response: do we just type the letters jwt as indicated in this post? And for the Auth header: do we just type the word Authorization as indicated in the post?
Hey there Dakshin thanks for reaching out, jumping in for Daniela, the JWT token in Auth Response will be in a different location based on where the provider puts as noted in the video. Each provider will have their own token method for this integration. https://www.loom.com/share/620a30bc74614e13925b0c05922fd5a9 The same is true for Authorization as well, each API has their own expected format for Authorization.
Thanks for jumping in! So for ZI, the JWT Auth Field Location, it sounds like we do just use the letters jwt. But for Auth Header, you mention that "each API has their own expected format for Authorization." For someone who is not familiar with the "standard HTTP guidelines" what should we be looking for in the provider's documentation to know when we've found the right thing to put?
Most providers will keep this information close to where the JWT Auth Field is located due to those being needed to run this integration. So the most likely place will be near were you find the data for JWT Auth Field, although will point out once again that this won't be the case for all providers, and some may not require an Authorization at all.
Are there resources for decoding errors when the JWT HTTP API integration fails? I did the best I could, but I just can't get it. My use case is that I'm trying to connect Clay to ZI. I have a list of accounts in my Clay table that I want to use my existing ZI integration to get contacts from those accounts in the table. Bonus if I could add criteria to the contact query so I am able to limit the contacts that get pulled in to my table.
Hey Sarah, thanks for reaching out about this. Happy to help! In this field you'd add in 'jwt' as it's a required input for the dynamic access token via API that ZI requires. After that, you can move down to mapping the API endpoint as you would regularly,here's a tutorial on how to map that part if it helps. https://downloads.intercomcdn.com/i/o/w28k1kwz/1245467653/8346c220f6f62d3fd260df53d4df/chrome_hGiDdiVbo4.png?expires=1731139200&signature=0f6a008eb66dfd0ac211559b7d36c9af61841a6aeb7eacc7de94ed19712e9a5c&req=dSIjE814modaWvMW1HO4zUdncDHMpKPKId7saGFXP3NsP8L4y2P6npHXFhVp%0AWjx3%0A You'll need to check out ZI's API docs and depending on which one you'd like to use, extracting the different parameters to map each required section and then adding your inputs. Let me know if you have additional questions or run into any issues though!
Thanks Arturo! I'm taking a look and hopefully this will be the help we need.
.png){kind=logo}
