Hello, I'm using Clay to automate ABM landing pages in Webflow but I'm running into 2 problems:
I'm retrieving the Logo URL and Fetching the image using Clay, but it's not sending the image to Webflow.
Instead of checking if there's a collection item already on Webflow and updating it, it's creating another item... which creates another slug
Thank you in advance for your help!
To address your issues with the Webflow integration, let's focus on updating existing items: 1. For updating collection items, use the "Update Collection Item with Webflow" action. This action requires: • Site • Collection • Item ID • Optional: Is draft, Is archived 2. To avoid creating duplicates, first use the "Get collection item" action to retrieve the existing item using its name or slug. Then, use the obtained Item ID in the update action. Regarding the logo image issue, the sources don't provide specific information. This might require further investigation. If you need more assistance, please request to talk to a person for in-depth troubleshooting of your Webflow integration setup.
Hey Rodrigo, thanks for getting in touch. Would you be able to share the Clay table you're working in? I'd like to have a look and make sure I understand the current setup you're working with.
Rodrigo, as a quick follow, wanted to share that we've raised this to our engineering group to have a look with us. It seems you're not the only one running into this, but we need to pin down exactly whey. I'm still interested to see the table you're working on. But I'll also keep tabs internally on our investigation, and let you know what I learn.
I used two different templates from Clay, and none of them seem to send the logo image to webflow https://app.clay.com/workspaces/339796/workbooks/wb_iTmQED2nJWuq/tables/t_Nknr46sNGgS8/views/gv_QhfTbDpfTtuJ https://app.clay.com/workspaces/339796/workbooks/wb_iTmQED2nJWuq/tables/t_CmeUNwRvNhDr/views/gv_4yrc7yX2x9Vw
also, another issue is if we already have 'uber' in Clay, and we add another 'uber' by mistake, or if we run the row again it creates another item on Webflow messing up with the slug... instead of hawksearch.com/customers/uber it will look like hawksearch.com/customers/uber-9238 or something like that ideally it should look if there's an item with the same name created on Webflow and don't create a new one. If we run the row again it should update it... instead of creating a new one
Thank you in advance Mark!
Additional help that I need, is when the Customer logo has a poor color contrast with white background we barely can read the title that uses their branded color... I wanted to create a rule to fallback to our brand color but it doesn't seem to work with color contrast. Can you provide a solution for that? here's the rule I was trying to work with
.png){kind=logo}
Check out this image of a company's logo and identify its primary color's hexcode. Return only the hexcode - nothing more, nothing less.
In case the color seems in the realm of white / gray / off-white or anything similar or if it's too close to white or black, then return this #FF7416 instead. Check if the color contrast ratio is 4.5:1 or above, 1 being white, if not use this #FF7416 instead.Snapchat color contrast scores 1.09:1 https://webaim.org/resources/contrastchecker/
To avoid creating duplicates, you should be able to "Get collection item", and then conditionall Create/Update based on the result. (Webflow's API doesn't allow for upsert, from what I can see.) I'd suggest handling that in a separate column, perhaps setting a "floor" color giving the background, and adjust upward as needed. I think the math for hex/rbg conversion needed to calculate contrast is probably more sophisticated than what could be handled. Maybe something more approximate like Euclidean distance between the two values would get you roughly 'close enough' in most cases. (Though I don't like not being sure that it's accessible.) I'm not sure if there are any handle WCAG APIs, but that's another option. If there were an endpoint where you could supply two hex values, and it would report back a contrast number, you could ping it using an HTTP API column in Clay. https://www.clay.com/university/lesson/http-api-clay-101 https://www.clay.com/university/guide/http-api-integration-overview I'll let you know of any new developments on the image side of things.
Dillon T. can you take a look on this?
My thought was to check for whether or not e.g. an ID was returned. If ID, update; if none, create.
ah okay yes that could work
seems to be working fine for creating a collection item. When we try to update I am getting an error message saying its failed to update item.
Thanks for this update. From our logs, it looks like the request itself is okay, and includes the required elements (collection_id and item_id).
https://developers.webflow.com/v2.0.0/data/reference/cms/collection-items/staged-items/update-item
Webflow is returning a 404/not found error: LBKS"message":"Requested resource not found","code":"resource_not_found","externalReference":null,"details":[]LBKSOn the Webflow side, would you be able to confirm those items are included in the site and collection referenced in the column settings? My hunch is that the combination of IDs isn't valid.
On the image front, any better results when using "Logo URL [input]" instead of "Company Logo URL"?
I was able to figure out why the error was presented - we had the company name in 2 fields, but I believe we only mapped one. after I changed that and ran, the update worked. Now our last trouble is with the logo. Let us know if there are any updates. Thanks!
When you edit the create/update columns, do you see any difference if you use the "Logo URL [input]" as the input, instead of "Company Logo URL"?
we tried using both columns but no change
Hey Rodrigo, thanks so much for reaching out! Our engineers pushed a fix on Friday for the issue that was preventing logos from being added to Webflow via the integration. Since we don’t have direct access to your Webflow account, we’re flying a bit blind here, but we’d love to make sure you get this working smoothly. When you get a chance, could you please share the following details with us? 1. The URL to the published Webflow page where you're trying to add the logo 2. The URL of the logo file you're attempting to upload through the integration 3. The URL to the Clay table where all of this is happening Once we have these, we’ll be able to dig in and start narrowing down what’s going on, and help you move forward from there. :)
Thank you Owen here are the details you asked: 1. The URL to the published Webflow page where you're trying to add the logo https://www.hawksearch.com/customer/uber 2. The URL of the logo file you're attempting to upload through the integration https://image-fetch.clay-run.workers.dev/?url=https://s3.amazonaws.com/media.mixrank.com/hero-img/31da6566d3d6eb818d173acad77e618a 3. The URL to the Clay table where all of this is happening https://app.clay.com/workspaces/339796/workbooks/wb_iTmQED2nJWuq/tables/t_Nknr46sNGgS8/views/gv_QhfTbDpfTtuJ I'm also sharing a video I recorded showing how it's connected on webflow
Mark L. When we made corrections to a record the "get collection item" did not rerun, but the "create collection item" did rerun creating a new collection item. I setup the run condition for create/update, but that won't matter unless the "get collection item reruns when we make a change to the record.
Hey, Thanks for sharing all the details and the video—it really helps clarify the issue. Just to make sure again it's clear, it would be much more efficient here to reach out to their team to try to understand what's wrong and why it's not making it's way there but here’s what I recommend based on what I saw:
1. Use the Clean Image URL The logo URL you’re using includes a proxy (image-fetch.clay-run.workers.dev). Instead, create a formula column that strips out the proxy part and just uses the direct S3 link. That often resolves formatting issues when uploading to Webflow.
2. Swap the Field in Webflow Integration Try using the Logo URL [input] field instead of Company Logo URL in the image upload section. This helps avoid referencing a broken or outdated value.
3. Watch Out for Commas in the URL One of the earlier issues seemed to come from a stray comma in the URL—make sure that’s removed. It caused logos not to appear even when everything else looked fine.
4. Check CMS Item Versions In Webflow, the CMS might have multiple versions of the same company. Some of those may not include the logo, while others do. You can explore the CMS items under the template pages in Webflow Designer to find the one pulling in the correct logo.
5. Manual Test Try uploading the same logo link directly into Webflow CMS manually. If it works there, but not through automation, it might point to a Webflow-specific limitation or bug. In that case, Webflow support would be the best next step. Let me know if you’d like help setting up that formula to clean the URL or anything else!