The moment it happens
Get an email before your Paddle API key expires
A week's warning before your key stops working, so you can replace it without any automation going quiet.
- Runs
- The moment it happens
- Apps
- Paddle
- AI
- Not needed
- Access
- notification settings
Send this to your assistant
Create a ClickRuntime automation: when Paddle says my API key is about to expire, email me at billing@mycompany.com with the key name and the expiry date.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A founder integrates Paddle with an internal dashboard, a billing sync and an accounting tool, each using an API key. Paddle keys can be set to expire, and when one does, the dashboard stops updating, invoices stop syncing and nobody can tell why until a customer complains about a missing receipt. Replacing a key is simple, but only if you know it is about to expire, and nobody puts key expiry dates in their calendar.
When Paddle sends its notification that an API key is about to expire, the event reaches ClickRuntime as soon as it is issued. An email is sent to you right away, naming the key and the expiry date, so you have time to create a replacement and update the tools that depend on it.
It is a small safety net for developers and finance teams whose revenue operations depend on Paddle integrations.
What you get out of it
Billing syncs keep running
A new key put in place before the old one expires means no gap in data flowing to your accounting and reporting tools. The alternative is missing days of transactions.
No surprise outages on a Monday
Keys often expire on days nobody is watching. A warning gives you time to rotate calmly during working hours, not in a rush when something has already broken. That planning also means you can test the new key before the old one stops working.
Customers still receive their invoices
Integrations that send receipts or provision access depend on a valid key. An early warning keeps customers from waiting on access they paid for. That is especially important for finance teams that depend on complete transaction records for reporting.
Good security practice is easier
Expiring keys are a safe habit, but they only work if people rotate them. A reminder makes regular rotation realistic, which limits the damage if a key ever leaks. That habit protects you in the long run, because shorter-lived credentials mean fewer old keys lying around.
The right person is told
The email goes to the address you choose, such as an engineering lead or finance contact. That avoids the warning going to someone who left the company. A shared mailbox is a good choice if several people maintain the integrations.
How it works
What happens, step by step
When one of your Paddle API keys is close to expiring, Paddle tells ClickRuntime.
ClickRuntime reads the name of the key and its expiry date.
You get an email naming the key and the date it expires, so you can replace it before anything stops working.
Before it runs live
- Connect Paddle
- Paste your automation's link into the other app's webhook settings
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
- Act only on the items that match your own rules, and skip the rest
- 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 Paddle steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, notify
@on_event
def handle(event):
body = event.json
if body.get("event_type") != "api_key.expiring":
return {"emailed": False}
key = body["data"]
notify.email_me(f"Paddle API key '{key['name']}' expires {key['expires_at'][:10]}",
f"Key: {key['name']}\nExpires: {key['expires_at']}\n"
"Create a replacement in Paddle > Developer tools > Authentication before then.")
return {"key": key["id"]}FAQ
Common questions
How far ahead does Paddle warn me?
Does it replace the key for me?
Do I need to set anything up in Paddle?
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
Announce new Paddle subscribers in Slack
Each new subscriber shows up in your channel with their plan and price the moment they sign up.
See how it worksHear about Paddle cancellations before they take effect
You learn when a customer schedules a cancellation, not just when access ends, so there's time to reach out.
See how it worksFlag declined Paddle payments in Slack
When a card is declined, you see who it was, how much and why, once per transaction even while Paddle retries.
See how it worksKeep exploring
Set up “Get an email before your Paddle API key expires” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.