Creating Smartlead campaign from Clay keep hanging on loading screen - how to fix?
Hey can you drop a URL for your table? Is it hanging on a loading screen when trying to save the enrichment or somewhere else?
This is the url table: https://app.clay.com/workspaces/156982/tables/t_EaYUyPWM1hEu/views/gv_EXvABzLunhkF It is hanging after I do this: ‘Create Smartlead Campaign’ -> Fill in Campaign, subject, body, email -> ‘Ok’ Then it stays hanging on the loading screen:
I tested with other tables too, and they give the same issue.
So seems just the connection between Clay - Smartlead not working?
I just updated Smartlead from a free trial subscription to a paid subscription, could that have caused this?
Is it possible that I can get a bit more attention on this issue? It's been 2 weeks now that we can not properly do our cold outbound.
Hey Jeroen W., we added some additional error catching and messaging here recently, and while checking out your issue again this looks still like its an API key issue. Additionally from the logs on this issue, the error being returned is 'API Key access denied'. This seems like an isolated incident, other users have been able to use the smartlead integration without any issue, so the signs point to this being an issue with your account or with your API key. If you DM me your API key, or if you schedule some time with me here https://calendly.com/maggie-williams-clay/30min I'll be able to help more
also if you are able to run the following curl command from your terminal curl "https://server.smartlead.ai/api/v1/campaigns?api_key={YOUR_API_KEY}" we will be able to tell if this is truly an API key issue or something else.
Have DMed!
Hi Jeroen, following up here for visibility. I was able to test your API key outside of the clay infrastructure, and this looks to definitely be an issue with Smartlead and the api key linked to your account, and not with the Clay-Smartlead integration. Unfortunately I can't resolve this, so I would recommend getting in touch with Smartlead support and reporting this issue to them as high-priority. Please keep us updated on how this develops and if you are able to resolve this issue with them!