Integrating Workato Webhook for Selective Clay Table Enrichment | Clay

Integrating Workato Webhook for Selective Clay Table Enrichment

Hi there, I’m currently enriching a Clay table via a webhook from Marketo that populates a few fields. This setup is working well and triggering enrichments correctly. Now, I’d like to send a second webhook from Workato to enrich additional fields in the same table, but only for selected rows. The idea is to match rows by email and update just the new field (e.g., phone number), without affecting the existing enrichment flow. Is it possible to:

Use a second webhook to update existing rows based on a unique field like email?
Ensure the original Marketo webhook/enrichment continues to run as is?
Eventually have both sets of enriched data (Marketo + Workato) returned in the same webhook response back to Workato?

24 comments

Channeled
APP
·
·
Yes, you can use a second webhook from Workato to update existing rows in your Clay table. Each Clay table has a unique webhook endpoint that can receive data programmatically from different sources. When you send data to your table's webhook URL, Clay will process it immediately, allowing you to enrich additional fields. Your setup would work as follows: ** Continue using your existing Marketo webhook to populate certain fields ** Set up a second webhook from Workato targeting the same table ** Use email as the matching field to update specific rows ** Both webhooks can operate independently without interference To implement this, you'll need to: 1. Copy your table's webhook URL 2. Configure Workato to send data to this URL 3. Include the email field in your payload for matching This approach allows both enrichment processes to run in parallel and update the same table.
Sources: Using Clay as an API | Documentation | Clay University Webhooks in Clay | Documentation | Clay University Import Data to Clay Using Webhooks
Smit V.
·
·
Hi there, thank you for reaching out! You can add another webhook source to the same table where you’re currently enriching data from Marketo. Just configure the new webhook to bring in data from Workato. You can then use the "Only run if" condition in your enrichment columns to control which enrichments run based on specific values. When you’re ready to send the fully enriched data back to Workato, use the HTTP API enrichment to push the data using Workato’s APIs. To add a new source, simply click the "+" icon next to the column header for the first column where WebHooks are being received. I hope this makes sense at a high level, let me know if you need any help implementing this :) - Smit
jasma m.
·
·
Thanks Smit 🙂
How do I add the formulae to only run this when received timestamp from source 2 & email is available?
Smit V.
·
·
Hi Jasma, You can click on the 'Use AI' button in the 'Only run if' condition section and type in natural language the run condition you want and make sure to link the columns by first typing '/' and selecting the column you are referencing. Could you try that, and let me know how it goes? If that doesn't work, reach back out and share your table link and I would be happy to take a look into it :)
jasma m.
·
·
https://app.clay.com/workspaces/352106/workbooks/wb_GN2rXgkw7hPq/tables/t_w4mZhHmTei3x/views/gv_CsT9zjZ8oQ75 Hi! I noticed that the formula currently pulls email data from Source 1. However, I only want to enrich phone numbers using emails from Source 2 — not Source 1. Do I need to create a separate email column for Source 2 in that case? Also, when I go to set up the mapping for source 2, it shows a lot more fields than I actually want to use for enrichment. Is there a way to limit or control that? Just to clarify, most emails in Source 2 may overlap with Source 1, but not always — and I want to make sure only Source 2 emails are used for phone enrichment. Thanks!
jasma m.
·
·
Hello, did you get a chance to check
Channeled
APP
·
·
Hey hey thanks for reaching out. Apologies for the delay in response. Ticket volume has been super high which causes delays at times. Looking at your table right now and will be right with you! Thanks for being super patient!
Channeled
APP
·
·
Hey! Just checked out your table, quick question, which source would be source 2? I can see your current condition is to run Enrich Person if email does not contain certain domains. Is this the formula you were referring to when it comes to enriching conditionally? Apologies for the back and forth but additional context would make it faster for me to troubleshoot. Thanks!
jasma m.
·
·
Workato is the source we wanna use for phone number
jasma m.
·
·
Any udpate?
LuisArturo
·
·
Hey there jumping in here, quick question taking a look at all of the values from you "Marketo" source there are currently only four which seem to be test since they are all from the same person, should all future imports from come from with a value for the "Webhook 2 Time stamp"? If yes then we can use this value as the condition for the integration to only run for the results form this source
(4 kB)
jasma m.
·
·
Sure that is right - I am trying to filter this to make sure only entried from this is enriched
LuisArturo
·
·
Then in this case this can be column that we can use inside of the "Conditional formula" for Marketo column so that it only runs on these rows. Something along the lines of "Only run if /Webhooks_2TiimesStamp" has a value will work.
jasma m.
·
·
Thanks I need help with formula - tried using AI but I guess my input is incorrect. I need this enrichment to only run if email id is new and not present (unfortunately - I am not able to control from workato's end and there can be multiple request from a single email id) so wanna make sure it doesn't run again.
jasma m.
·
·
Any update?
Bo (.
·
·
Hey, How are you currently determining if the email is new AND not present in the table? That’ll help figure out the best way to set up the formula to prevent duplicate enrichments. Let me know and I’ll guide you from there.
jasma m.
·
·
Not resolved
jasma m.
·
·
/I guess I ned help with that how do I make sure clay enriches data only for new email address & not lates? Do I need to add extra column
Bo (.
·
·
Hey there, I can help you set up a formula to prevent duplicate enrichments based on email address. Since you want to make sure the enrichment only runs for new emails that aren't already present, here's what you can do: First, you'll need to create a counter to track duplicate emails using this method: https://www.loom.com/share/a39a4569d95244b7886026f3c70812c7
The formula would be: {{Unique ID}}?({{Lookup Multiple Rows in Other Table}}?.records?.findIndex(r=> r['Unique ID']?.toString()==={{Unique ID}}?.toString())> -1?{{Lookup Multiple Rows in Other Table}}?.records?.findIndex(r=> r['Unique ID']?.toString()==={{Unique ID}}?.toString())+1::2)::2
Then in your enrichment's "Only run if" condition, you'd use: LBKSOnly run if /count is equal to 1LBKSThis way, the enrichment will only run for the first occurrence of each email address and skip any duplicates that come through later.
Let me know if you have more questions.
jasma m.
·
·
Apologies for not replying early, I actually created another table so that we have different data getting pushed and credits are not used.
jasma m.
·
·
I am still working on this - I will let you know if I still need any help thanks
Bo (.
·
·
Perfect - Keep us posted - Happy Thursday
jasma m.
·
·
Thanks now we have another problem for some reason data pushed by clay in showing under input in workato instead of payload - https://app.clay.com/workspaces/352106/workbooks/wb_0swq8lj9q6fa6NK5qKd/tables/t_0swq8orxbCHT6ykhB6N/views/gv_0swq8osyXAvd42nDgXX
Bo (.
·
·
Hey — the issue here is likely related to how Workato parses incoming requests. When Clay sends the request, the structure is wrapped under the "input" key in your body: LBKS{ "action": "updateOnly", "lookupField": "email", "input": { "email": "{{email}}", "clayphonenumber": "{{Mobile Phone (US and Canada)}}" } }LBKSSo in Workato, the values you’re expecting in the payload will actually show under the input object. That’s why you’re seeing them in the input field. If you want those fields directly in the payload, just remove the "input" wrapper and place the key-value pairs at the top level: LBKS{ "action": "updateOnly", "lookupField": "email", "email": "{{email}}", "clayphonenumber": "{{Mobile Phone (US and Canada)}}" }LBKSUpdate that in the body of your HTTP request in Clay, and Workato should parse the values as expected. Let me know if you have more questions.
(342 kB)