Daily

Get a warning when Lusha credits run low

An email lands before my team runs out of Lusha credits mid-campaign.

Runs: Daily
Apps: Lusha
AI: Not needed
Access: API key

Send this to your assistant

Create a ClickRuntime automation: every day at 8am, check my Lusha credit balance and email me if fewer than 100 credits are left.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Lusha charges by credit, and a team that burns through its allowance mid-month finds out at the worst time: a rep trying to look up a hot prospect is told there are no credits left. The number sits in an admin page that few people open, so the first sign of a shortfall is a blocked workflow and a scramble to buy more or wait for the reset.

Every day, ClickRuntime calls Lusha's usage endpoint, compares what has been used with the total and with the threshold you set, and emails you if credits are running low. On a day when everything is fine, it stays silent, so the message only appears when it is worth reading.

Sales managers and operations leads who share one Lusha plan among several reps benefit most.

What you get out of it

Reps are never blocked unexpectedly
A warning a week before credits run out gives you time to top up or slow the usage. A rep stuck in front of a hot prospect with no credits loses the lead.
Spending can be planned
Knowing the rate of use over the month helps you decide whether the plan fits your team. You can upgrade on your terms rather than in a panic. That puts the budget conversation in your hands.
Misuse or waste is noticed
A sudden drop in credits may mean a large bulk run or a user looking up far more contacts than expected. Daily checks catch that within a day. Catching that early saves real money.
Budget owners stay informed
The person who pays for the plan receives the warning, not just the person who uses it. That keeps decisions about buying more credits close to the budget. That keeps the money decision where it belongs.
No daily monitoring is needed
Nobody has to remember to open the usage page. The check runs on its own and speaks up only when there is something to act on. That makes the check reliable, not dependent on habit.

How it works

What happens, step by step

Once a day, ClickRuntime checks how many Lusha credits your account has used and how many are left.
If fewer than 100 credits remain, you get an email saying how many are left and how many have been used.
If there are enough credits, nothing is sent.

Before it runs live

Connect Lusha

What you get

RunsDaily

Get a warning when Lusha credits run lowtoday, 9:00Succeeded

Email · Lusha creditsLusha credits running low: 64 credits left (936 of 1,000 used).

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Lusha steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

credit_usage_alert.pyexample

from clickruntime import on_trigger, credentials, notify, http

MIN_CREDITS = 100

@on_trigger
def run(event):
    resp = http.get("https://api.lusha.com/account/usage",
                    headers={"api_key": credentials.secret("LUSHA_API_KEY")})
    resp.raise_for_status()
    usage = resp.json()["usage"]
    left = usage["total"] - usage["used"]
    if left < MIN_CREDITS:
        notify.email_me("Lusha credits running low", f"{left} Lusha credits left ({usage['used']} of {usage['total']} used).")
    return {"credits_left": left}

FAQ

Common questions

What threshold should I set?

A common choice is 20 percent of the monthly allowance remaining, or enough credits for a week of normal use. Look at your average daily usage and set the warning so that it gives you several days to react. The email states how many credits remain.

Will it warn me once or every day?

It can be set either way. Many teams like a single warning when the threshold is crossed and another at a lower level, to avoid a daily message that people learn to ignore. Mention the levels you want when you set it up.

Can it warn a teammate as well?

Yes. The email can go to several people, such as the sales manager and the finance contact. Some teams also post to Slack, so reps know to be careful with lookups when the balance is low.

What permissions does it need?

API key. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Weekly