Issue with Smartlead API Key and Contact Enrollment Error | Clay

Issue with Smartlead API Key and Contact Enrollment Error

Hey, i've been using smartlead for years and now all of a sudden i get this problem when enrolling contacts: Getting the same error for Heyreach API key too. looks like all api keys aren't working in clay I updated the API key with Wrenly info but still keep getting this error...

57 comments

Clay
APP
·
·
Since you updated your API key but are still getting errors, here are the most common causes: For Smartlead API Key Issues: ** Ensure you're using the correct API key from your Smartlead settings at app.smartlead.ai/app/settings/profile ** Add the API key to your integration account in Clay under the Integrations section Common reasons leads aren't being added: ** "Allow Duplicates" is turned off and you're trying to add duplicate leads ** Leads are already blocked in your Smartlead account * You've reached your account's lead limit If you encounter a 401 "invalid API key" error, double-check you have the correct API key in your Clay settings. Could you share the specific error message you're seeing so I can provide more targeted help?
Sources: Smartlead integration overview | Documentation | Clay University Write to Other Table | Documentation | Clay University
Ali K.
·
·
API key is not working either: https://app.clay.com/workspaces/243114/workbooks/wb_PoekMYe5NH7N/tables/t_smDvY3ttByrT/views/gv_mQNeWGuSaiyW Getting the same error for Heyreach API key too. looks like all api keys aren't working in clay
Ali K.
·
·
I tried the new API key (from smartlead, it had changed for some weird reason) so i copied and paste into clay to sync the 2 accounts up, but still says it could not verify?
Gabe E.
·
·
Hi Ali, Taking a closer look now.
Gabe E.
·
·
Is there anything you changed recently in Smartlead or this account that you think may have caused the issue?
Ali K.
·
·
hey
Ali K.
·
·
nope, looks like all apis are failing
Ali K.
·
·
because it's smartlead and heyreach
Ali K.
·
·
i didn't change anything
Gabe E.
·
·
I'm poking around the backend now. To confirm, you didn't change anything and suddenly smartlead and heyreach stopped working?
Ali K.
·
·
yep
Ali K.
·
·
and thenn i tried to update the API keys (bc it said that was the only way to fix it) .... by copying and pasting it in... trying to fix it.... and it still won't connect
Gabe E.
·
·
I just ran through one of the error messages and it looks like your accounts expired. Do you mind checking this in their portals and letting me know if there's an issue there? Message: ** Error: 401 Unauthorized ** Message: "Plan expired!" ** Root Cause: Your SmartLead subscription has expired What's Happening: ** Your API key is actually working correctly (it's authenticating) ** SmartLead is rejecting requests because your *account plan has expired
Ali K.
·
·
hmmm let me check this
Ali K.
·
·
Ali K.
·
·
Weird let me contact support
Gabe E.
·
·
Please let me know how this goes!
Ali K.
·
·
thanks - any tips on what to do when hitting 100 rows. Do i need to start everything over again and clean it up?
Ali K.
·
·
Or is there a way to extend the limit slightly
Ali K.
·
·
it is working, messaged support and checked this issue
Gabe E.
·
·
For the 100 columns, we recommending using Send table data or Write to table to send the info to another table and keep building there.
Ali K.
·
·
and fixed it.
Ali K.
·
·
For heyreach, I'll check now again too. weird they both weren't working
Gabe E.
·
·
There is not way to extend at this time unfortunately due to performance concerns .
Gabe E.
·
·
Please let me know if you're still having issues and how else I can help here! Gabe
1
Ali K.
·
·
amazing, thanks Gabriel
Gabe E.
·
·
I'm so glad you were able to find a fix here!
Gabe E.
·
·
(:
Gabe E.
·
·
I'm going to go ahead and close the ticket. Feel free to message back here to re-open the chat!
Gabe
Ali K.
·
·
Hey Gabriel!
Ali K.
·
·
Now my open AI integration isn't working 😢
Ali K.
·
·
Could you check on this? column is "3D Action Figure Image Prompt
Ali K.
·
·
I see this when i test the api seperately but in the clay table i keep seeing error
LuisArturo
·
·
Hey there Ali thanks for reaching out, jumping in for Gabe, to confirm here this is for the "Inbound LEadfinder table correct?
Ali K.
·
·
Yep
Ali K.
·
·
Nice to meet you and thanks for your help
LuisArturo
·
·
Quick question here, for the rows that ran did you use the Clay key or your own?
Ali K.
·
·
Always used open AI key
Ali K.
·
·
All of a sudden it stopped working, had this same table for over a year
LuisArturo
·
·
Ok so not seeing an error when running rows, but do see it in the connection setup here. Another question is the error appearing when running multiple rows here?
(14 kB)
Ali K.
·
·
Ali K.
·
·
It says that error… but when I click manager and set it up it says success (see above)
Ali K.
·
·
But it keeps showing this error like it’s not set up successfully when it is
LuisArturo
·
·
Ok thank you for clarifying, I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Ali K.
·
·
Good morning LuisArturo & Gabe E., It looks like GPT is successfully connected (see screenshot) but inside the clay table it says it can't connect to api: I was due to launch some campaigns yesterday, because our clay credits were expiring but couldn't due to this error. Can I get the remaining clay credits added back. Also even more importantly, do you know roughly when your engineering team can figure out the issue or start to take a look at it?
Gabe E.
·
·
Hi Ali, Thanks for flagging this! Are you seeing certain problem rows/areas? I'm looking at your OAI column and seeing prompt input error messages (below). If you highlight the problem rows/area I'm happy to take a closer look!
(167 kB)
Gabe
Ali K.
·
·
Hey Gabe, i'll make them optional but i don't think this is the reaosn because i quadruple checked these fields in clay for the contact and they're all populared
Ali K.
·
·
actually, before I do that, you can see for yourself that the contact I'm trying to generate them for "charlie nevill" has all the data
Ali K.
·
·
It also keeps saying this on that contacts row, when i generate image
Ali K.
·
·
But as i showed in the previous image, it is successfully connecting but contradicting itself...
Gabe E.
·
·
Hi Ali,
Looking at the logs, this seems to be a LinkedIn image access issue. Here's what I'm seeing: ** Error: 403 deny-expired-url from [media.licdn.com](http://media.licdn.com) ** Problem: Clay is trying to fetch a LinkedIn profile photo that has an expired URL ** URL: The LinkedIn image URL contains ?e=1752710400 (expiration timestamp) What's Happening: 1. Clay is attempting to download a LinkedIn profile photo 2. The LinkedIn CDN URL has expired (LinkedIn URLs have time-based expiration) 3. LinkedIn is blocking access with a 403 Forbidden error 4. This breaks your image generation workflow Why This Happens: ** LinkedIn URLs expire after a certain time period (usually days/weeks) ** Old scraped data contains expired image links ** Clay's image generator can't access the source image Solutions: Option 1: Use Fresh LinkedIn Data ** Re-scrape LinkedIn profiles to get current image URLs ** Use Phantombuster or Captain Data for fresh profile photos Option 2: Download Images First ** Save LinkedIn images to Clay's storage when first scraped ** Use Clay's image hosting instead of external LinkedIn URLs Quick Fix: Check your LinkedIn profile photo column - you'll likely see expired URLs from old data. Re-enriching those profiles should resolve the issue.
Gabe E.
·
·
Please let me know how this sounds and how else I can help here! Gabe
Ali K.
·
·
Thank you so much
Ali K.
·
·
why is this error misleading us on this quest?
Ali K.
·
·
Any reason this came up?
Gabe E.
·
·
Thanks Ali! I'll flag this as a bad error message. This comes up with the "charlie.nevill" cell?
Gabe E.
·
·
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.