Building an Integration with Clay for Enhanced Data Enrichment | Clay

Building an Integration with Clay for Enhanced Data Enrichment

i wanted to build a integration with Clay with my service. Say i have a table in clay table with list of people. Wanted to add enrichment column with my service and show corresponding config parameter options. How can i build that integation?

5 comments

Channeled
APP
·
·
To build an integration with Clay for your enrichment service, you'll need to follow a similar pattern to our existing integrations: 1. Create an enrichment that users can add to their tables by clicking "Add enrichment" while in a Clay table. 2. Your integration should appear under the "Integrations" section in the enrichment menu. 3. When users select your integration, they'll see a modal where they can: • Select or add an account (API key) • Configure input parameters (like name, employer, etc.) • Set optional auto-update settings • Add conditional run criteria if needed • Choose which data to add as columns to their table The enrichment should transform data by pulling additional information from your service, similar to how our existing integrations work with RocketReach, Leadmagic, and others. For specific integration requirements or to discuss partnership opportunities, please request human assistance by clicking on "Talk to a person."
Sources: Enrow integration overview | Documentation | Clay University Enrichments | Documentation | Clay University RocketReach integration overview | Documentation | Clay University Leadmagic integration overview | Documentation | Clay University RocketReach integration overview | Documentation | Clay University
Devi C.
·
·
Say my clay table has 100 people. I have 3 apis
create_list
add_lead
sync_list
i needed to first call create_list and get list id and then use that list id for all 100 people from the clay table and then finally once all 100 people add_lead is done, i needed to call sync_list api. How can i do that?
Owen C.
·
·
Hey Devi, thanks for reaching out! You can use our HTTP API column to call first call the endpoint "create_list" using it's corresponding method and headers, which should return the list ID depending on how you've set up this API. Then you can use another HTTP API column, the endpoint for "add_lead" and the method + input for how you uniquely identify leads within your environment to then push this to the ID that is returned by the initial "Create List" endpoint. A quick tutorial on our HTTP API column can be found here. :) Let me know if this makes sense / is in the right direction!
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
Devi C.
·
·
Yeah i wanted to let clay create_list and sync_list before and after of entire table execution. That too they are called only once. Yes I am aware of using Http api Column for add_lead. Are you saying i should create 3 columns for each of the api even though create_list & sync_list should only be called once? wondering if clay has a hooks to call certain apis start and end of the runs