Skip to content

AI agent automations

AI agent automations that outlast the conversation

Agents are good at writing the job. They are not good at staying awake to run it. ClickRuntime gives your assistant a place to put that job, with your approval in the loop.

Works with Claude Code, Codex, opencode, Any MCP client and other AI assistants.

ChatGPTClickRuntime connected
Create a ClickRuntime automation: watch our competitor's pricing page and tell me in Slack whenever a plan price changes.
I'll check the page every 6 hours, remember the current prices, and post the difference to #market when one changes.
Competitor pricing watchLive
When
Every 6 hours
Uses
competitor.example.com, Slack
AllowReview
Runsapp.clickruntime.com
Competitor pricing watch06:00Succeeded · 1.6s
Last run06:00 · No change

Details

The missing piece for agents

An AI assistant can write a script that checks a page, summarizes a feed or calls an API. When the chat ends, the work stops. ClickRuntime is the runtime underneath: the assistant saves the job, turns it on with your approval, and we keep it running on a schedule or whenever an outside event arrives.

Approval is built in

An agent can build, turn on, run, test and fix an automation until a run succeeds. Each of those actions goes through your AI assistant's own permission prompt, so you approve every step. Before running something live, the agent tells you what it will do in outside services. Keys and secrets are added only by you in the ClickRuntime dashboard, and deleting an automation needs a separate confirmation.

Keys never pass through the model. When a job needs one, the assistant sends you to the ClickRuntime dashboard to save it, and the script reads it from the environment at run time.

Works with any MCP assistant

ClickRuntime is an MCP connector. Add it once to ChatGPT, Claude, Claude Code, Cursor or any assistant that supports remote MCP servers with OAuth, sign in, and ask in any conversation. The server is https://clickruntime.com/api/mcp. The connect guide shows the steps for each assistant.

What we refuse to run

The assistant declines jobs that are harmful or that we can't run responsibly: malware, secret monitoring of a person, collecting credentials, getting around another service's access controls or rate limits, moving money or placing trades, and collecting health, government ID or payment card data.

Try asking

Prompts to start with

Paste one of these into a chat with ClickRuntime connected.
  • Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.

  • Create a ClickRuntime automation: when a new row is posted to my form's webhook, classify it as sales, support or spam and route it to the right Slack channel.

  • Create a ClickRuntime automation: every Friday at 4pm, email me a summary of what changed on these three documentation pages this week.

Apps

Works with the apps you use

Connect an app once and every automation in your workspace can use it. If it has an API, a webhook or a web page, it works.
  • Slack
  • Google Calendar
  • Shopify
  • Notion
  • Telegram
  • Asana
  • Dropbox
  • Calendly
  • WordPress
  • QuickBooks
  • Bitbucket
  • Evernote
  • Square
  • Wix
  • Mailgun
  • Sentry
  • MySQL
  • Firebase
  • Cloudflare
  • Instagram
  • Spotify
  • Miro
  • Substack
  • Product Hunt
  • Pinterest
  • Etsy
  • Wise
  • Gusto
  • RSS feeds
  • Google Sheets
  • Stripe
  • Typeform
  • Airtable
  • Jira
  • Mailchimp
  • Discord
  • Zendesk
  • WhatsApp
  • Google Docs
  • Figma
  • Box
  • WooCommerce
  • Squarespace
  • Brevo
  • Datadog
  • MongoDB
  • Vercel
  • X
  • YouTube
  • Google Analytics
  • Confluence
  • Ghost
  • Mastodon
  • TikTok
  • eBay
  • Coinbase
  • Okta
  • Gmail
  • GitHub
  • HubSpot
  • Google Drive
  • Trello
  • Zoom
  • Linear
  • Intercom
  • Xero
  • GitLab
  • Todoist
  • PayPal
  • BigCommerce
  • Webflow
  • PagerDuty
  • PostgreSQL
  • Supabase
  • Netlify
  • Facebook
  • Reddit
  • Google Ads
  • Bitly
  • Medium
  • Bluesky
  • Twitch
  • Revolut
  • Zoho
  • Auth0
View all apps

FAQ

Questions about ai agent automations

Can the agent turn things on by itself?
Yes, with your approval. It can turn an automation on, run it, test it and apply changes, and your AI assistant asks for your permission before each of those actions. It can't add keys or secrets, and deleting needs a separate confirmation.
Does the AI run on every execution?
No. The assistant writes the script once. Each run executes that script directly, which is faster, cheaper and predictable. If the script calls an AI API, it does so with your own key.
Which agents are supported?
Any assistant that supports remote MCP servers with OAuth, including ChatGPT, Claude, Claude Code and Cursor. Connect it to https://clickruntime.com/api/mcp.
Does ClickRuntime see my conversations?
No. We receive only the tool calls the assistant makes, such as the draft automation and its schedule. We don't receive or store your chat history.
Can I stop an automation quickly?
Yes. Ask the assistant to pause it, or press Pause in the ClickRuntime dashboard. A paused automation keeps its script, history and trigger link.

Set up your first automation in ChatGPT or Claude

Free plan. No credit card.