Scheduled Python without the AWS plumbing
Lambda with EventBridge Scheduler is a solid way to run code on a timetable, once you've set up the role, the package, the schedule, the secrets and somewhere to keep state. ClickRuntime does all of that for each automation, and your AI assistant writes the script.
- 01 IAM execution role and policies+1
- 02 Deployment package with dependencies+1
- 03 EventBridge schedule and its role+1
- 04 Secrets Manager or env vars for keys+1
- 05 DynamoDB table for state+1
- 06 CloudWatch alarm for failures+1
6 resources
1 run
Why people move small jobs off Lambda
Nothing to provision
No roles, policies, packages or schedule resources. An automation is a script, a schedule or trigger link, and its keys.
State built in
Each automation keeps its own state and counters. No DynamoDB table or S3 object to set up for “what did I see last time”.
Built from the assistant you already use
Ask in ChatGPT, Claude, Cursor or any MCP client. It writes the automation, tests it and fixes it.
Keys stay out of code
Secrets are saved in the ClickRuntime dashboard, read by the script when it runs, and masked in every log.
Failures reach you
Every run is logged with output and errors, and you get an email when one fails. No alarm to configure.
Unlimited users
Plans are per workspace. Invite the whole team at no extra cost.
A 14-step workflow becomes one sentence
Workflow builders make you place every trigger, filter, branch and formatter yourself, then fix it when one breaks. Here you describe the result and your assistant writes the code.
- 01 Shopify trigger
- 02 Filter > $500
- 03 CRM: find
- 04 Router
- 05 Path A: new
- 06 Path B: existing
- 07 Formatter
- 08 AI: summarise
- 09 Text parserfailed
- 10 Slack: post
- 11 CRM: add note
- 12 Error handler
- 13 Set variable
- 14 Delay 2 min
“When a Shopify order over $500 comes in, check the customer in HubSpot. If they're new, post to #sales with an AI summary of the order. Otherwise add a note to their contact.”
Here's the automation. It runs on each new order.
- When
- Shopify · new order (webhook)
- Uses
- Shopify, HubSpot, Slack and AI
AWS Lambda + EventBridge and ClickRuntime compared
| Topic | AWS Lambda + EventBridge | ClickRuntime |
|---|---|---|
| Setup | Function, IAM role, schedule, schedule role, secrets, logs and alarms | Describe the job in your AI assistant |
| Languages | Python (3.11 and later supported), Node.js, Java, .NET, Ruby, Go and custom runtimes | Python 3.11 |
| Shortest interval | rate(1 minute) in EventBridge Scheduler | Every 5 minutes |
| Timezone | IANA timezones on cron schedules | IANA timezones, in plain words |
| Run length | Up to 900 seconds (15 minutes) | Short jobs: a time limit per run |
| State | Another service, such as DynamoDB or S3 | Built into every automation |
| Webhooks | Function URLs or API Gateway; you write the signature check | Trigger link with signature checks for Stripe, GitHub, Shopify, Typeform and HMAC |
| Cost | Lambda: 1M requests and 400,000 GB-seconds a month free. Scheduler: 14M invocations free, then $1.00 per million | 250 runs a month free; paid plans from $9 for 2,000 runs |
| Team access | IAM users and roles | Unlimited users per workspace |
AWS Lambda + EventBridge or ClickRuntime?
Choose AWS Lambda + EventBridge when
- The job is heavy: more memory, longer runs up to 15 minutes, or high volume where per-request pricing wins.
- It needs to reach things inside your AWS account: a private VPC, RDS, SQS or S3 buckets with IAM permissions.
- Your team already manages infrastructure as code and wants the job alongside the rest.
Choose ClickRuntime when
- The job calls public APIs and should just run: reports, syncs, alerts, webhook handlers.
- You don't want to own a role, a package and a table for a 40-line script.
- Non-engineers should be able to ask for changes from their AI assistant.
Move from AWS Lambda + EventBridge in five steps
Your assistant does the rewriting, you check the result.
- Step 1Pick a functionStart with a scheduled or webhook function that calls public APIs. Copy its code and note its schedule expression and timezone.
- Step 2Ask your assistant to rebuild itConnect ClickRuntime to ChatGPT, Claude or Cursor, paste the handler code and schedule and say what should happen. It saves a draft you can read before anything runs.
- Step 3Save your keys in the ClickRuntime dashboardSecrets from Secrets Manager or environment variables don't move over. Save each API key as a secret in the ClickRuntime dashboard, or sign in through the app's OAuth. Keys never go into the chat.
- Step 4Test itYour assistant turns the automation on, runs it once or sends a test event, and fixes it until the run succeeds. Run both side by side for a few days if you like.
- Step 5Switch the old one offDisable the EventBridge schedule (or remove the function URL from the sender), then delete the function, role and table when you're sure.
This Lambda runs on an EventBridge schedule. Move it to ClickRuntime.
- Daily signups reportWeekdays 8:00 · Ready
- Stripe refunds alertTrigger link · Ready
- Image resizingStays on Lambda · Needs a key
One job, moved from AWS Lambda + EventBridge
“Move this Lambda to ClickRuntime: every weekday at 8:00 London time, count signups from our API in the last 24 hours and post the number to #metrics in Slack, with the change from the day before.”
Where each AWS Lambda + EventBridge piece goes
| In AWS Lambda + EventBridge | In ClickRuntime |
|---|---|
| lambda_handler(event, context) | A function with the @on_trigger or @on_event decorator |
| EventBridge Scheduler schedule | A schedule in plain words, in your timezone |
| Function URL or API Gateway route | Trigger link, with signature checks |
| Secrets Manager / environment variables | Secrets saved in the ClickRuntime dashboard |
| DynamoDB or S3 for state | state.get and state.set |
| Deployment package or layer | Up to 15 pinned PyPI packages declared with the script |
| CloudWatch logs and alarms | Run log, plus an email when a run fails |
Send us your function code and schedule. We'll help you move it.
Email it with a line about what each one does. A person reads it, tells you how it maps to ClickRuntime, and helps until your automations are running.
Email your function code and schedule
Leave out API keys and other secrets.
What you can add next
Once the first job is moved, these are the changes people usually ask for next. Each is one message to your assistant, not a new service to set up.
- Trigger links
Handle Stripe refunds on a trigger link with the signature checked for you
“Add a trigger link automation that Stripe calls on charge.refunded, checks the signature and posts the amount and reason to #finance.”
- Memory between runs
Keep a 30-day history of counts without a database
“Change my signups report so it keeps the last 30 daily counts and includes the 7-day average.”
- Built-in AI
Summarise yesterday's signup sources in one line
“Change my signups report so it adds one line on where yesterday's signups came from, based on the referrer field.”
- Any app or API
Add new signups to HubSpot as contacts
“Add to my signups report: create a HubSpot contact for each new signup that isn't there yet.”
- Multi-step logic
Skip weekends and holidays from the comparison
“Change my signups report so Monday compares with Friday, not Sunday.”
- Schedules
Run a month-end summary on the 1st
“Add to my signups report: on the 1st of each month at 9, email me last month's total and the best week.”
Moving from AWS Lambda + EventBridge
Is ClickRuntime serverless like Lambda?
Yes. Scripts run on AWS Lambda behind the scenes, but ClickRuntime sets up and manages everything around them: schedule, trigger link, secrets, state, logs and alerts.
Can I use Python packages?
Yes. Common ones such as requests, the Google and Slack clients, feedparser and BeautifulSoup are available, and an automation can declare up to 15 pinned PyPI packages.
Can it reach my VPC or RDS database?
No. Scripts make outbound HTTPS calls to public addresses only. Keep jobs that need private AWS resources on Lambda.
How long can a run take?
ClickRuntime is for short jobs with a time limit per run. If a job needs close to 15 minutes, Lambda is the better fit.
Do I need to know how to code?
No. You describe what should happen and your AI assistant writes, tests and fixes the Python. You can read every version in the ClickRuntime dashboard.
What does ClickRuntime cost?
The free plan includes 250 runs a month with webhooks, code and AI. Paid plans start at $9 a month for 2,000 runs, with unlimited users. A scheduled check that finds nothing new and sends nothing isn't counted.
Will you help me move my functions?
Yes. Email hello@clickruntime.com with what each functions does, or the Lambda code or config, and we'll help until it's running. Never send API keys or other secrets.
Move your first AWS Lambda + EventBridge automation today
Free plan. No credit card.