Daily
Get warned at 75% of your Cloudinary credits
You get one email when monthly credit use passes the percentage you chose.
- Runs
- Daily
- Apps
- Cloudinary
- AI
- Not needed
- Access
- API key + secret
Send this to your assistant
Create a ClickRuntime automation: check my Cloudinary usage every morning and email me once when credits used go past 75% of my plan this month.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Cloudinary bills in credits, and the standard warning at 90% often arrives too late to do anything useful. A marketing team runs a campaign with heavy video transformations, a developer ships an unoptimized gallery, and by the time the plan is nearly used up there are only a few days left in the billing month and no budget to cover them.
Each day, this reads your Cloudinary usage, works out the percentage of your credits consumed, and alerts you the first time it passes the level you choose, here 75%. It remembers which thresholds it has already reported in the current month, so you get one clear message per level rather than a daily reminder.
Teams with spiky media workloads, such as e-commerce stores around a sale, find an early warning most valuable, because it leaves room to optimize or upgrade calmly.
What you get out of it
Get a warning with time left to act
At 75% there are still days or weeks of the month left. That is enough time to compress images, cache transformations or agree to a higher plan, without the pressure of a service limit.
Avoid surprise overage or throttled delivery
Running out of credits can mean extra charges or blocked transformations on a live site. A custom threshold keeps those outcomes off the table by giving someone time to respond. Shipping an unoptimized gallery on the last day of the month is far more costly than finding it a week earlier and fixing it.
Match the alert to your own risk tolerance
A 90% default may suit a stable site but not a launch week. Choosing the threshold yourself means the alert reflects how fast your usage can actually climb. A launch week or a sale can double usage in days, so a lower threshold gives you notice that a default level would miss.
Find the cause while it is recent
If usage jumped in the last few days, the cause, such as a new page or an import, is easy to trace. An early alert shortens that investigation. Finding out about growth in the same week it started makes the cause, such as a new page or a bulk import, easy to trace.
Give finance a predictable number
Budget owners can see in advance if the month will exceed plan. That avoids a conversation about an unplanned bill after the invoice has already arrived. Budget owners can see in advance that the month will run over, and plan for it, instead of reacting to a bill.
How it works
What happens, step by step
Every day, ClickRuntime checks how many of your monthly Cloudinary credits you have used.
If usage has passed 75%, you get an email with the percentage and the credits used out of your limit.
You are warned only once per month, so the daily checks stay quiet after the first alert.
Before it runs live
- Connect Cloudinary
What you get
Build your own
Need it to work differently?
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 Cloudinary steps into one automation
Under the hood
The code that runs this automation
from datetime import date
from clickruntime import on_trigger, credentials, http, state, notify
CLOUD = "your-cloud-name"
@on_trigger
def run(event):
usage = http.get(f"https://api.cloudinary.com/v1_1/{CLOUD}/usage",
auth=(credentials.secret("CLOUDINARY_API_KEY"), credentials.secret("CLOUDINARY_API_SECRET"))).json()
pct = usage["credits"]["used_percent"]
month = date.today().strftime("%Y-%m")
if pct >= 75 and state.get("alerted_month") != month:
notify.email_me(f"Cloudinary credits at {pct:.0f}%",
f"{usage['credits']['usage']:.1f} of {usage['credits']['limit']} credits used this month.")
state.set("alerted_month", month)
return {"used_percent": pct}FAQ
Common questions
Does the alert repeat every day once I pass 75%?
Which usage does Cloudinary count toward credits?
Can I add a second alert at 90%?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Receive a weekly Cloudinary usage summary
Every Monday you see storage, bandwidth and transformations next to last week's figures.
See how it worksPost new Cloudinary uploads to Slack
Your team sees each new image or video as soon as it is uploaded.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Get warned at 75% of your Cloudinary credits” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.