Skip to main content

Enrow isn't working in Clay: how to fix it

Most Enrow errors in Clay come from an empty Enrow balance or a changed API key. Here is what to check, in order.

Written by Thomas Lucy

If Enrow stops working in Clay, check your Enrow credit balance first. When your balance is empty, Clay often shows a vague error, such as "Unable to connect with Enrow", instead of saying that you are out of credits.

This article is for Enrow runs paid with your own Enrow credits (your own account or an HTTP API column). If you pay with Clay credits, contact Clay support.

1. Check your Enrow credit balance

  1. Log in to Enrow and look at CREDITS at the bottom of the left menu. The balance is updated in real time, including the searches made from Clay.

  2. If the balance is at zero or very low, add credits: buy a pay-as-you-go pack or renew your plan early. See What happens when you run out of credits.

To see what Clay used, go to Analytics and set the Origin filter to API. Searches made from Clay count as API searches. A Clay table that runs on many rows, or runs again, can use a lot of credits quickly. See Check your credit balance and usage.

Tip: Turn on automatic top-up and a low credit alert, so your Clay tables never stop.

2. Check your API key

  • You reset your Enrow API key. The old key stopped working at once. Copy the new key from API in the left menu and paste it in Clay: in your Enrow account connection and in every HTTP API column. See Find, copy or reset your API key.

  • In an HTTP API column, the key must be in a header named exactly x-api-key, not Authorization, with no space in the header name.

  • The API page says "API access not included in your plan". The API needs a paid plan. See API access: which plans include it and how to test the API.

3. Read the error code

In an HTTP API column, Clay shows the error code that Enrow returned:

  • 401: the API key is missing, wrong or was reset. See step 2.

  • 402: not enough credits. See step 1.

  • 400: a required field is missing, such as the full name.

  • 429: too many requests at once. Run the column more slowly and try again.

  • 500: a problem on Enrow's side. Try again a little later.

If the column only returns an id and no email, this is normal: the Enrow API is asynchronous. See Use Enrow in Clay to get the result back.

For the full list, see API error codes and how to fix them.

4. Some rows find nothing

  • Check that the company domain is right, or try the company name instead.

  • Send full names, with the last name.

  • Some people have no professional email that can be found.

A search that finds nothing costs nothing. Learn more in How to improve your Email Finder find rate.

Still stuck?

Related articles

Did this answer your question?