← Back to Skills Marketplace
byungkyu

zoho-mail

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
15211
Downloads
8
Stars
0
Active Installs
14
Versions
Install in OpenClaw
/install zoho-mail
Description
Zoho Mail API integration with managed OAuth. Send, receive, and manage emails, folders, and labels. Use this skill when users want to send emails, read messages, manage folders, or work with email labels in Zoho Mail. 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 Mail connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Mail 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 Mail examples; they add no Zoho Mail capability - Zoho Mail is not an event source, a trigger cannot read Zoho Mail 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
Install only if you intend to connect Zoho Mail through Maton. Confirm the exact account before authorizing, review every send/delete/update before it runs, and be especially careful with hosted functions, triggers, or destinations because they can keep running or forwarding data until removed.
Capability Assessment
ℹ Credentials
Network access, OAuth, and email data access are sensitive but proportionate for a mail API integration; raw API-key HTTP use is documented as a fallback only when the CLI cannot be installed.
✓ Install Mechanism
Installation uses pinned Maton CLI or SDK packages and does not include hidden scripts, obfuscated payloads, or arbitrary remote execution in the skill artifact.
✓ Instruction Scope
The instructions default to read/list calls, require explicit user approval for new connections and all writes, and limit hosted functions/triggers to user-approved automation.
ℹ Persistence & Privilege
OAuth tokens, hosted functions, triggers, and destinations can persist beyond a single run, but the artifact clearly discloses this, requires user approval, and gives cleanup guidance.
✓ Purpose & Capability
The documented capabilities match the stated purpose: read, send, search, and manage Zoho Mail messages, folders, labels, and attachments through Maton.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install zoho-mail
  3. After installation, invoke the skill by name or use /zoho-mail
  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.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.6
- Updated all endpoint URLs to use https://api.maton.ai/ instead of https://gateway.maton.ai/ and https://ctrl.maton.ai/ - Revised connection management instructions to reflect the new endpoints and clarified usage of the Maton-Connection header. - Added a Security & Permissions section emphasizing explicit user approval for write operations. - Removed the LICENSE.txt file from the repository.
v1.0.5
No changes detected in this version. - No updates or modifications were made to the skill.
v1.0.4
- Added "homepage" field to metadata, linking to the Maton homepage. - No other changes detected.
v1.0.3
- Added a new metadata section to declare emoji (🧠) and required environment variable (MATON_API_KEY) under the "clawdbot" key. - No changes to core functionality, API reference, or user instructions. - Documentation and description remain unchanged except for the updated metadata.
v1.0.2
- No changes detected in this version. - Functionality, documentation, and configuration remain the same as the previous release.
v1.0.1
- Skill name corrected from "zohomail" to "zoho-mail" in SKILL.md. - No code or feature changes detected; documentation only.
v1.0.0
- Initial release of Zoho Mail skill with managed OAuth integration. - Send, receive, search, and manage emails, folders, and labels in Zoho Mail via Maton API gateway. - Full documentation on authentication, connection management, and API usage included. - Supports multiple connections with selectable active connection via header. - Examples provided for all major email, folder, and label operations.
Metadata
Slug zoho-mail
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 14
Frequently Asked Questions

What is zoho-mail?

Zoho Mail API integration with managed OAuth. Send, receive, and manage emails, folders, and labels. Use this skill when users want to send emails, read messages, manage folders, or work with email labels in Zoho Mail. 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 Mail connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Mail 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 Mail examples; they add no Zoho Mail capability - Zoho Mail is not an event source, a trigger cannot read Zoho Mail 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 15211 downloads so far.

How do I install zoho-mail?

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

Is zoho-mail free?

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

Which platforms does zoho-mail support?

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

Who created zoho-mail?

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

💬 Comments