Step by step
You ask for an automation in chat. We run it.
Once
Connect your assistant
Add ClickRuntime to ChatGPT, Claude, Claude Code, Cursor or any MCP client with one server URL, then sign in with Google or your email. You do this once.
Your assistant can now see your workspace and save drafts. It can't turn anything on by itself.
1 · Ask
Describe the job in plain words
Say what should happen, when, and where the result goes. The assistant asks for anything missing, such as your timezone or which Slack channel.
It then writes a short Python script using the ClickRuntime SDK and saves it as a draft. A draft does nothing.
2 · Set up
Connect the apps it needs
If the job needs an app's API key, you save it in the ClickRuntime dashboard as a secret. If the app uses sign-in, such as Slack or Google, you add your own app for it once and then sign in.
Keys never go into the chat. The assistant only ever sees their names.
3 · Deploy
It deploys and tests it
Your assistant deploys the automation, runs it once to test it, and fixes and redeploys until a run succeeds. Before a live run it tells you what it will send or change outside ClickRuntime.
You allow each step in your assistant's own permission prompt.
- When
- Every hour
- Reads
- acme.com/pricing
- Sends
- Slack · #market
- AI
- Summarise changes (included)
- Uses
- ~720 runs a month
4 · Runs
It runs on our servers
On a schedule from every 5 minutes to monthly, in your timezone, or when an app sends an event to its trigger link. You can close the chat and your laptop.
Every run is logged with its output, with secrets masked. Failures are emailed to you.
Each automation keeps its own state between runs, such as the last value it saw or the items it already handled, so it can act only on what's new or changed. See stateful automations.
5 · Change
Change it by asking
“Move it to 7:30.” “Also send it to email.” Your assistant applies the change and tests it, and every version is listed in the ClickRuntime dashboard.
You can ask to go back to an earlier version at any time.
6 · Fix
When something breaks, ask for a fix
If an app changes its API or a key expires, the run fails and you get an email with the error. Ask “why did it fail?”. Your assistant reads the same run log you see.
It fixes the script, redeploys and runs it again until it works.
What runs where
Your assistant writes it. We run it.
| Where | What happens there |
|---|---|
| Your AI assistant | Understands your request, writes the script, saves drafts and answers questions about runs. It receives only what ClickRuntime's tools return. |
| ClickRuntime | Stores the script, schedule, secrets and the state each automation keeps between runs. Runs each automation separately from every other one, and keeps the run history. |
| Your apps | Receive calls from the script with your keys (Slack, Google, Stripe and others), or send events to the automation's trigger link. |
Safety and data
How your keys and data are handled
Secrets
Saved in the ClickRuntime dashboard, encrypted and write-only, so nobody can read a value back. Only your automations can use them, and they're masked in logs.
Your control
You allow each action in your assistant's own permission prompt. Keys are added only by you in the ClickRuntime dashboard, deleting needs your confirmation, you can pause any automation at any time, and every run is logged.
Runs and alerts
Every run is logged with its output and any errors. Events from other apps can be checked so that only genuine ones start a run.
Details are in the privacy policy and the script reference.
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.