ClickRuntime for opencode
From an opencode session to a live webhook or cron job
Ask opencode to catch webhooks from your payment provider, run a sync every night, or watch a page for changes. ClickRuntime runs it for you with run history, retries and alerts, whichever model you use in opencode.
About 2 minutes to connect. Free plan, no credit card.
Setup · about 2 minutes
Connect ClickRuntime to opencode
Add ClickRuntime to opencode.json in your project, or to ~/.config/opencode/opencode.json for every project.
{ "$schema": "https://opencode.ai/config.json", "mcp": { "clickruntime": { "type": "remote", "url": "https://clickruntime.com/api/mcp" } } }Sign in. Your browser opens the ClickRuntime sign-in; choose a workspace and approve.
opencode mcp auth clickruntimeCheck it's connected, then start opencode and ask for an automation.
opencode mcp list
Try it
A first automation to ask opencode for
run scripts/sync_customers.py every night at 2 on clickruntime and email me the row count
- A draft is savedopencode 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 opencode closed, and tells you when something fails.
What people do with it
Automations people set up from opencode
Watch a competitor's pricing page
Checks a pricing page every hour and posts a short summary to Slack only when something changes.
Log Stripe payments to Google Sheets
Every successful Stripe payment is added as a new row in a Google Sheet within seconds.
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.
Post yesterday's Shopify orders to Slack
Every weekday at 9, yesterday's order count and revenue are posted to your sales channel.
Weekly revenue summary from Stripe
Every Friday at 17:00 you get an email with the week's revenue, new customers and cancellations.
More things to ask opencode
Run scripts/sync_customers.py every night at 2 on ClickRuntime and email me the row count.
Create a ClickRuntime automation: watch our pricing page and tell me in Slack when anything on it changes.
Create a ClickRuntime automation: set up a webhook for Paddle subscription events that logs cancellations to a sheet.
Create a ClickRuntime automation: show the last 10 runs of my nightly sync and anything unusual in the logs.
Apps
Apps your opencode 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 opencode
opencode can build, deploy, run, test and change an automation, and keeps fixing it until a run succeeds. You allow each action in opencode'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 opencode you confirm through a one-time link that opens ClickRuntime in your browser.
After it's live
Checking on and changing automations from opencode
Check status
Ask whether an automation ran, when it runs next and how its recent runs went. opencode lists your automations with their state: live, paused or needing setup.
Ask opencode“Which of my ClickRuntime automations failed in the last 24 hours?”
Find out why a run failed
opencode 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 opencode“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. opencode applies the new version, tests it and tells you what changed. Every version is kept.
Ask opencode“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 opencode“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 opencode“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 opencode“List automations that haven't succeeded this month and delete the old test ones.”
Help
opencode: troubleshooting and questions
Still stuck? See troubleshooting or contact support.
Checking the connection
Removing it
Does it matter which model I use in opencode?
Sign-in fails or loops. How do I debug it?
How do I approve actions?
Related pages
Keep exploring
opencode is a trademark of SST. ClickRuntime is not affiliated with SST.