← Back to Skills Marketplace
byungkyu

zoho-calendar

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
14324
Downloads
4
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install zoho-calendar
Description
Zoho Calendar API integration with managed OAuth. Manage calendars and events with full scheduling capabilities. Use this skill when users want to read, create, update, or delete calendar events, manage calendars, or schedule meetings. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Zoho Calendar connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Calendar action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Zoho Calendar examples; they add no Zoho Calendar capability - Zoho Calendar is not an event source, a trigger cannot read Zoho Calendar data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, understand that this skill can manage and delete Zoho Calendar data through your Maton-connected account and can set up persistent functions or triggers if you approve them. Use read-only actions first, confirm every write/delete/automation, keep trigger destinations on Maton-controlled hosts unless you explicitly trust another host, and do not expose Maton API keys or OAuth credentials.
Capability Assessment
ℹ Credentials
Network access, OAuth login, OS credential-store use, and a raw API-key fallback are proportionate for a hosted API integration, and the artifact instructs agents not to inspect, export, log, or persist credentials.
✓ Install Mechanism
Installation is a documented Maton CLI install through pinned npm/Homebrew instructions; the artifact itself is Markdown reference material and ships no executable scripts.
ℹ Instruction Scope
The package includes shared trigger catalog references for other apps such as Gmail and Linear, but the main skill and each reference file explicitly state that those files do not widen Zoho Calendar capability and should only be used when the user asks for that source by name.
ℹ Persistence & Privilege
OAuth tokens, hosted functions, triggers, destinations, and watch checkpoints can persist beyond a single call, but the skill describes those flows plainly, prefers DENY_ALL network policy, requires separate approval for writes and automations, and warns about persistent data forwarding.
ℹ Purpose & Capability
The skill supports Zoho Calendar read/write/delete operations plus optional Maton-hosted functions and triggers; these are high-impact capabilities but they match the stated calendar and scheduling purpose and are repeatedly gated on user confirmation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install zoho-calendar
  3. After installation, invoke the skill by name or use /zoho-calendar
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.4
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.1
- Removed redundant documentation file skill-card.md. - No changes to functionality or user experience. - Documentation and API usage remain unchanged.
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.4
- Base API URLs updated from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for a unified endpoint. - Instructions, request examples, and code snippets revised to use the new api.maton.ai URLs. - Security & Permissions section added: highlights the need for explicit user approval for all write operations. - Connection management documentation simplified and references to /connections endpoints updated for the new base URL. - LICENSE.txt file removed from the project.
v1.0.3
- Added a clawdbot metadata block specifying emoji and required environment variable (MATON_API_KEY) in SKILL.md. - No changes to API or user-facing functionality. Documentation update only.
v1.0.2
No user-facing changes in this version. - Internal version update only; no file changes detected.
v1.0.1
No user-facing changes in this release; documentation metadata only.
v1.0.0
Initial release of Zoho Calendar API skill with managed OAuth integration. - Provides full CRUD operations for Zoho calendars and events, including recurring events and attendee management. - Supports listing, creating, updating, and deleting both calendars and events. - API key authentication via Maton; easy OAuth connection management. - Includes Python examples for all actions using the API gateway. - Allows header-based selection for multiple Zoho Calendar accounts. - Comprehensive documentation and usage instructions provided in SKILL.md.
Metadata
Slug zoho-calendar
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 13
Frequently Asked Questions

What is zoho-calendar?

Zoho Calendar API integration with managed OAuth. Manage calendars and events with full scheduling capabilities. Use this skill when users want to read, create, update, or delete calendar events, manage calendars, or schedule meetings. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Zoho Calendar connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Calendar action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Zoho Calendar examples; they add no Zoho Calendar capability - Zoho Calendar is not an event source, a trigger cannot read Zoho Calendar data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 14324 downloads so far.

How do I install zoho-calendar?

Run "/install zoho-calendar" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is zoho-calendar free?

Yes, zoho-calendar is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does zoho-calendar support?

zoho-calendar is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created zoho-calendar?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.

💬 Comments