ClickRuntime for Codex
Let Codex leave behind jobs that keep running
Codex finishes the task; ClickRuntime keeps the follow-up going. Handle every GitHub or Stripe webhook as it arrives, sync data each night, or poll an endpoint every five minutes, with run history and alerts and nothing to deploy.
About 2 minutes to connect. Free plan, no credit card.
Setup · about 2 minutes
Connect ClickRuntime to Codex
Add the server from your terminal. The CLI, the IDE extension and the Codex app all read the same config.
codex mcp add clickruntime --url https://clickruntime.com/api/mcpSign in. Your browser opens the ClickRuntime sign-in; choose a workspace and approve.
codex mcp login clickruntimePrefer editing config? Add this table to ~/.codex/config.toml (or .codex/config.toml in a trusted project) instead of the first command.
[mcp_servers.clickruntime] url = "https://clickruntime.com/api/mcp"Start Codex and run /mcp. clickruntime is listed with its tools. In the Codex app, it shows under Settings → MCP servers.
Try it
A first automation to ask Codex for
run the invoice reconciliation in scripts/reconcile.py every night at 1 utc on clickruntime
- A draft is savedCodex calls ClickRuntime and saves a draft. A draft does nothing on its own.
- You connect what it needsSlack, Google or an API key are connected once in the ClickRuntime application. Keys never go into the chat.
- You stay in controlYou allow each action in your assistant's permission prompt. Before a live run it tells you what starts it and every service it will contact. Every run is logged.
- It runs on its ownIt keeps running on ClickRuntime's servers with Codex closed, and tells you when something fails.
What people do with it
Automations people set up from Codex
Triage new GitHub issues
Each new issue gets an AI summary and suggested label, posted to your team's Slack channel.
Check SSL certificates before they expire
Every Monday, your domains' certificates are checked and you get an email if any expire within 14 days.
Log Stripe payments to Google Sheets
Every successful Stripe payment is added as a new row in a Google Sheet within seconds.
Weekly revenue summary from Stripe
Every Friday at 17:00 you get an email with the week's revenue, new customers and cancellations.
Watch a competitor's pricing page
Checks a pricing page every hour and posts a short summary to Slack only when something changes.
Post yesterday's Shopify orders to Slack
Every weekday at 9, yesterday's order count and revenue are posted to your sales channel.
More things to ask Codex
Move the cleanup step in scripts/nightly.py to ClickRuntime and run it every night at 1 a.m. UTC.
Create a ClickRuntime automation: create a webhook endpoint for Stripe invoice.paid events that appends the amount and customer to my Revenue sheet.
Create a ClickRuntime automation: every 5 minutes, call https://api.example.com/health and email me if it fails three times in a row.
What failed in my ClickRuntime runs this week, and what would you change?
Apps
Apps your Codex automations can use
- Slack
- Google Calendar
- Shopify
- Notion
- Telegram
- Asana
- Dropbox
- Calendly
- WordPress
- QuickBooks
- Bitbucket
- Evernote
- Square
- Wix
- Mailgun
- Sentry
- MySQL
- Firebase
- Cloudflare
- Spotify
- Miro
- Substack
- Product Hunt
- Etsy
- Wise
- Gusto
- RSS feeds
- Google Sheets
- Stripe
- Typeform
- Airtable
- Jira
- Mailchimp
- Discord
- Zendesk
- 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
- Google Ads
- Bitly
- Medium
- Bluesky
- Twitch
- Revolut
- Zoho
- Auth0
Your control
What you control in Codex
Codex can build, deploy, run, test and change an automation, and keeps fixing it until a run succeeds. You allow each action in Codex's own permission prompt, and before a live run it tells you what it will send or change outside ClickRuntime. Keys are added only by you in the ClickRuntime dashboard, you can pause any automation at any time, and every run is logged.
Deleting needs one more step: in Codex you confirm through a one-time link that opens ClickRuntime in your browser.
After it's live
Checking on and changing automations from Codex
Check status
Ask whether an automation ran, when it runs next and how its recent runs went. Codex lists your automations with their state: live, paused or needing setup.
Ask Codex“Which of my ClickRuntime automations failed in the last 24 hours?”
Find out why a run failed
Codex reads the run's error and log lines, explains them in plain words and proposes a fix. You also get an email when a run fails.
Ask Codex“Show me the logs from the last failed run and fix the script.”
Change what it does
Move the time, add a recipient or change the logic. Codex applies the new version, tests it and tells you what changed. Every version is kept.
Ask Codex“Make the health check time out after 10 seconds instead of 30.”
Pause and resume
Pausing takes effect immediately, and you can pause from the ClickRuntime dashboard too. Events sent while paused are kept.
Ask Codex“Pause every automation that calls the staging API.”
Run it now
Trigger a one-off run to test a change or catch up after an outage. The schedule stays as it is, and the run counts toward your monthly runs.
Ask Codex“Run the scraper once now and show me the output.”
Clean up
Find automations you no longer need and delete them. Deleting removes the automation, its runs and its trigger link, so you confirm it first.
Ask Codex“List automations that haven't succeeded this month and delete the old test ones.”
Help
Codex: troubleshooting and questions
Still stuck? See troubleshooting or contact support.
Sign-in does not open a browser
Project config is ignored
Removing it
Does it work in the Codex IDE extension and the app?
How is this different from a Codex cloud task?
Where do API keys go?
Can Codex turn an automation on by itself?
Related pages
Keep exploring
Codex is a trademark of OpenAI. ClickRuntime is not affiliated with OpenAI.