How to connect Cronly to OpenClaw
Connect Cronly to OpenClaw with ClawLink: paste your Cronly key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
CronlyAPI KEYMCPCronly monitors cron jobs, SSL certificates, servers, and crontab backups and reports operational alerts.. Once connected, OpenClaw can read and act on Cronly from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Cronly access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Cronly setup: install one ClawHub skill, connect Cronly in the browser, and OpenClaw can call real Cronly actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Cronly.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Cronly
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Cronly?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Cronly in the ClawLink dashboard — paste your Cronly API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Cronly, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Cronly is connected in the dashboard, that agent calls the same 10 Cronly tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Cronly MCP for OpenClaw
Looking for a Cronly MCP server for OpenClaw? ClawLink connects Cronly to OpenClaw and exposes 10 Cronly tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Cronly integration works the same way.
What the OpenClaw Cronly integration can do
10 Cronly tools are ready for OpenClaw once the account is connected. The 7 below are the ones people reach for most; your agent can call all 10.
7 of 10 Cronly tools for OpenClaw
| Tool | What it does |
|---|---|
Get company cronly_get_company | Return safe organization, timezone, and subscription-summary fields for the connected Cronly |
Get resource cronly_get_resource | Get one monitor, project, certificate, user, server, or backup by its resource identity |
List resources cronly_list_resources | List notifications, monitors, projects, certificates, users, servers, or backups |
Create certificate cronly_create_certificate | Create an SSL/TLS certificate-expiry monitor for a hostname and port |
Create monitor cronly_create_monitor | Create a cron-job heartbeat monitor and return its ID and sensitive pulse token |
Create project cronly_create_project | Create a project for organizing Cronly monitors and certificate checks |
Pulse monitor cronly_pulse_monitor | Record a successful heartbeat for a monitor using its sensitive pulse token |
Try it: find the Cronly tool you need
Browse the 7 Cronly tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Cronly, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Cronly, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Cronly, group them by priority, and recommend what OpenClaw should do next.
Create it in Cronly for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cronly working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Cronly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cronly account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Cronly. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Cronly actions to the runtime in a format your agent can reliably use. | 10 tools for Cronly are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Cronly to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Cronly in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Cronly key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Cronly skill but can't call the tools
The ClawHub skill teaches OpenClaw about Cronly, but the calls run through the ClawLink plugin and your connected account. Make sure Cronly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Cronly from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Cronly tools
Cronly tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Cronly call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Cronly returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Cronly has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Cronly integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Cronly: link your Cronly account once in the browser and OpenClaw can call the Cronly API through 10 ready-made tools — no custom code or token handling.
How do I add Cronly to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cronly skill from ClawHub, then you click Connect in the dashboard to authorize Cronly. OpenClaw calls the tools from the next message — no config files, and the Cronly key you paste is stored server-side instead of in your environment.
How long does it take to connect Cronly to OpenClaw?
About two minutes. Sign in, click Connect next to Cronly in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Cronly up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cronly working from chat.
OpenClaw installed the Cronly skill but can't call the tools
The ClawHub skill teaches OpenClaw about Cronly, but the calls run through the ClawLink plugin and your connected account. Make sure Cronly is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.