Resolving Invalid YouTube Input Error in Clay API Integration

Hi Clay Support, I’m working on enriching YouTube influencer profiles by adding the profile URL via various API integrations. However, when I attempt to run this process, I receive an “invalid YouTube input” error—even though I’m using what appears to be the correct profile URL format. Could you please advise on how to resolve this issue or let me know if there’s a specific format or method required for YouTube profile URLs in Clay? Thank you!

7 comments

Channeled
APP
·
·
To resolve the "invalid YouTube input" error when enriching influencer profiles, make sure you're using the correct format for YouTube profile URLs. The error likely occurs because the Profile URL field hasn't been properly mapped. For YouTube channels, use the full channel URL format: https://www.youtube.com/channel/CHANNEL_ID or https://www.youtube.com/c/CHANNEL_NAME If you're still encountering issues after verifying the URL format, double-check that you've correctly mapped the Profile URL field in your Clay table before running the enrichment process. If you need further assistance, please request human support by clicking on "Talk to a person" in this chat.
Sources: Enrich YouTube Channel with YouTube | Clay.com Claybooks: Find, Qualify, and Contact Influencers from YouTube, Instagram, or TikTok | Clay.com
Bo (.
·
·
Hey—can you share the table URL so we can take a closer look? Also, double-check the column settings to make sure the correct field is mapped. This error usually happens when the wrong input is selected—make sure it’s specifically mapped to a YouTube URL field. If it still looks off, let us know what it says in the input prompt.
(52 kB)
Ori M.
·
·
Bo (. here you go https://app.clay.com/workspaces/576188/workbooks/wb_0sw9o2cyKDTgcMiee32 Again this is the input, it worked before not sure what happened now
Ori M.
·
·
thanks
Bo (.
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Bo (.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
👀1
Ori M.
·
·
will check thank you!