Seems to be bug in Nybmlr Find Work Email integration

Seems to be bug in Nybmlr Find Work Email integration | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
No, there isn't a bug in the Nimbler Find Work Email integration. The integration works as designed, allowing you to find someone's work email using either a LinkedIn URL or a combination of company name and full name. When using our Clay-managed Nimbler account, you'll be charged 2 credits per enriched cell.The integration automatically updates every 24 hours by default, though you can disable this if needed. You also have the option to set conditional run criteria to control when the enrichment runs. Sources: Find Work Email with Nimbler Nimbler - Clay University
Keegan Dunford
·
·
https://app.clay.com/workspaces/10589/workbooks/wb_BJbgKXMaZ2ZC/tables/t_CIfOLpEMGA1u/views/gv_K7gj2wusgTec All these rows ran successfully and the data hasn't changed but if you click rerun any of the successful rows you'll get the error
Loading attachments
Channeled
APP
·
·
When you encounter errors in the Find Work Email process, it's important to note that you should only rerun the rows that haven't run or have errors. To do this correctly, go to your first waterfall column and use the "Run all rows that haven't run or have errors" option. This ensures you only process the entries that weren't completed, avoiding duplicate runs on already successful searches.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bo (Clay)
·
·
Hey there! I took a look at the table, and it seems the issue may be with your API key rather than Clay itself - I noticed it's working when we use Clay credits but hitting some errors with your API. I've also checked on the backend and couldn't see anything wrong. Would you mind double-checking your account status with Nybmlr? They'll be able to tell you if there's anything going on with your API key that's causing these errors when you try to rerun rows. Let me know what you find out and I'll help get this sorted! 😊
Channeled
APP
·
·
Hi Keegan Dunford! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
No, there isn't a bug in the Nimbler Find Work Email integration. The integration works as designed, allowing you to find someone's work email using either a LinkedIn URL or a combination of company name and full name. When using our Clay-managed Nimbler account, you'll be charged 2 credits per enriched cell.The integration automatically updates every 24 hours by default, though you can disable this if needed. You also have the option to set conditional run criteria to control when the enrichment runs. Sources: Find Work Email with Nimbler Nimbler - Clay University
Keegan Dunford
·
·
https://app.clay.com/workspaces/10589/workbooks/wb_BJbgKXMaZ2ZC/tables/t_CIfOLpEMGA1u/views/gv_K7gj2wusgTec All these rows ran successfully and the data hasn't changed but if you click rerun any of the successful rows you'll get the error
Loading attachments
Channeled
APP
·
·
When you encounter errors in the Find Work Email process, it's important to note that you should only rerun the rows that haven't run or have errors. To do this correctly, go to your first waterfall column and use the "Run all rows that haven't run or have errors" option. This ensures you only process the entries that weren't completed, avoiding duplicate runs on already successful searches.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bo (Clay)
·
·
Hey there! I took a look at the table, and it seems the issue may be with your API key rather than Clay itself - I noticed it's working when we use Clay credits but hitting some errors with your API. I've also checked on the backend and couldn't see anything wrong. Would you mind double-checking your account status with Nybmlr? They'll be able to tell you if there's anything going on with your API key that's causing these errors when you try to rerun rows. Let me know what you find out and I'll help get this sorted! 😊
Channeled
APP
·
·
Hi Keegan Dunford! This thread was recently closed by our Support team. If you have a moment, please share your feedback: