The provider alert bells
Setup catches an unready account before you start. These bells catch a provider that stops once you're up and running.
There are seven: three for Apify, and two each for BrightData and Gemini.
Each rings at most once a day while the cause holds. Each one reaches the account managers of the affected clients, plus everyone who can manage your provider keys. Those key-holders get an email too.
On a rejected-key bell, only the people who can manage your provider keys get the steps to paste a new one. Everyone else is told those people have been asked to replace it.
Apify
Your Apify plan needs attention. Your Apify account has no active paid plan, so some collection and analysis can't run. Everything resumes once it's on a paid plan.
Fix: put the Apify account back on a paid plan. See getting your Apify key.
Your Apify usage limit was reached. Your Apify account hit its monthly usage limit, so everything that runs on Apify is paused until the next billing period or until you raise the limit in Apify under Billing, Limits. The limit is also your spending cap, so raise it only as far as you're comfortable paying.
Fix: raise the limit in Apify, or wait for the next billing period.
Your Apify key was rejected. Apify refused the key Huntit uses, so everything that runs on Apify has stopped. Copy a fresh API token from Apify under Settings, API & Integrations, and paste it in Settings under Credentials. Everything resumes once it's saved.
Fix: paste a new Apify API token in Settings → Credentials. See getting your Apify key.
BrightData
Your BrightData account needs attention. Your BrightData account is suspended or out of funds, so scraping has stopped. It resumes once the account is funded and active again.
This is the one to act on quickly. While the account is down, collection stops: no new posts are found, and posts you already track can miss check-ins. A short gap only delays new posts; posts from a longer one are gone for good.
Fix: add funds or clear the suspension in BrightData.
Your BrightData key was rejected. BrightData refused the key Huntit uses, so scraping has stopped. In BrightData, create an API key with Admin permission that never expires, and paste it in Settings under Credentials. Scraping resumes once it's saved.
Act on this one quickly too, for the same reason.
Fix: paste a new Admin key in Settings → Credentials. See getting your BrightData key.
Gemini
Your Gemini account is out of credits. Your Gemini key has no usable credits, so AI analysis has stopped. New posts still arrive, and analysis resumes once your Google AI Studio account has credits.
Fix: buy credits in Google AI Studio, then re-test the key. See out of Gemini credits.
Your Gemini key was rejected. Google refused the Gemini key Huntit uses, so AI analysis has stopped. New posts still arrive. Create a new key in Google AI Studio and paste it in Settings under Credentials. Analysis resumes once it's saved.
Fix: paste a new Gemini key in Settings → Credentials. See getting your Gemini key.
How they behave
- Where a click lands. Every bell opens Settings → Credentials, where that provider's row shows the problem until it's fixed.
- They clear themselves. Fix the cause and the bell stops ringing. The row returns to
Verifiedat its next check, or at once if you re-test.
For what the states on those rows mean, see reading your key states.