ClickRuntime for Zed
Code from Zed, live behind a webhook or on a schedule by lunch
Ask Zed's agent to handle Shopify and GitHub webhooks as they arrive, run a function hourly, or check an endpoint before standup. ClickRuntime hosts it with state between runs, retries and email alerts, so your editor can stay closed.
About 2 minutes to connect. Free plan, no credit card.
Setup · about 2 minutes
Connect ClickRuntime to Zed
Open Settings → AI → MCP Servers, select Add Server, then Add Remote Server.
Settings → AI → MCP Servers → Add Server → Add Remote Server
Name it clickruntime and paste the server URL. Don't add an Authorization header.
https://clickruntime.com/api/mcpOr add it to your settings.json directly.
{ "context_servers": { "clickruntime": { "url": "https://clickruntime.com/api/mcp" } } }Zed opens the ClickRuntime sign-in in your browser. Choose a workspace and approve; the dot next to clickruntime turns green.
Try it
A first automation to ask Zed for
run fetch_rates every morning at 6 on clickruntime and write it to my Rates sheet
- A draft is savedZed 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 Zed closed, and tells you when something fails.
What people do with it
Automations people set up from Zed
Post yesterday's Shopify orders to Slack
Every weekday at 9, yesterday's order count and revenue are posted to your sales 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.
Triage new GitHub issues
Each new issue gets an AI summary and suggested label, posted to your team's Slack channel.
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.
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 Zed
Create a ClickRuntime automation: run the fetch_rates function in this file every morning at 6 and write the result to my Rates sheet.
Create a ClickRuntime automation: make a webhook endpoint for Shopify orders/create that posts big orders to #sales.
Create a ClickRuntime automation: before standup each weekday, check our staging /healthz and email me only if it's slow.
Which of my ClickRuntime automations ran today, and did any fail?
Apps
Apps your Zed 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 Zed
Zed can build, deploy, run, test and change an automation, and keeps fixing it until a run succeeds. You allow each action in Zed'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 Zed you confirm through a one-time link that opens ClickRuntime in your browser.
After it's live
Checking on and changing automations from Zed
Check status
Ask whether an automation ran, when it runs next and how its recent runs went. Zed lists your automations with their state: live, paused or needing setup.
Ask Zed“Which of my ClickRuntime automations failed in the last 24 hours?”
Find out why a run failed
Zed 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 Zed“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. Zed applies the new version, tests it and tells you what changed. Every version is kept.
Ask Zed“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 Zed“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 Zed“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 Zed“List automations that haven't succeeded this month and delete the old test ones.”
Help
Zed: troubleshooting and questions
Still stuck? See troubleshooting or contact support.
Checking the connection
Removing it
Will the agent run the job on my machine?
How do I approve actions from Zed?
Where do API keys go?
Related pages
Keep exploring
Zed is a trademark of Zed Industries. ClickRuntime is not affiliated with Zed Industries.