Guides
ClickRuntime docs
How to set up automations by asking your AI assistant, and how to look after them in the ClickRuntime dashboard.
ClickRuntime runs automations after the conversation is over. You describe a job to your AI assistant. The job runs on a schedule ("every hour", "weekdays at 9") or when something arrives (a payment, a form, a webhook). ClickRuntime stores it, runs it on its own servers and keeps a record of every run.
You'll mostly use ClickRuntime through your AI assistant. The ClickRuntime dashboard is where you save secrets, manage billing and teammates, and check on things.
Start here#
- Connect ClickRuntime to your AI assistant and sign in.
- Ask for an automation in plain language.
- If the assistant asks for a connection or a secret, follow Connections and secrets.
- The assistant turns it on and runs a test. Your AI assistant asks for your permission before each of those steps.
Not sure where to start? Browse the templates for ready-made automations you can ask for by name.
What ClickRuntime is for#
Built-in assistant features, such as scheduled tasks and reminders, are great for reminders and prompts that answer inside the chat. Use ClickRuntime when the job has to:
- run real code, such as calling an API, parsing a page or doing arithmetic on data,
- use outside services with your own keys or a connected account,
- deliver outside the chat, by email or to Slack,
- react to an outside event through a trigger link,
- remember things between runs, such as the last value it saw, the items it already handled or a running count. See State between runs.
Words we use#
| Word | Meaning |
|---|---|
| Automation | One named job, with a schedule or a trigger link, a plain-language summary and the script that does the work |
| Draft | Saved but not running. Drafts never do anything on their own |
| Live | Running on its schedule, or accepting events on its trigger link |
| Paused | Stopped by you. It keeps its script, history and trigger link |
| Run | One execution, with a result and a log |
| Trigger link | The URL that receives outside events for one automation |
| Secret | A key or token you save in the ClickRuntime dashboard. The assistant only sees its name |
| Connection | An account you authorize on the provider's own consent screen, through an app your workspace added, or Slack for notifications |
| Monthly runs | How many runs your workspace's plan includes each month |
Reference#
The script reference covers the Python runtime the assistant writes against: handlers, payloads, state, notifications, signature checks, packages and limits. It's also available as raw markdown.