← Back to Skills Marketplace
byungkyu

Zoho CRM

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
15046
Downloads
6
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install zoho-crm
Description
Zoho CRM API integration with managed OAuth. Manage leads, contacts, accounts, deals, and other CRM records. Use this skill when users want to read, create, update, or delete CRM records, search contacts, manage sales pipelines, access organization settings, manage users, or retrieve module metadata in Zoho CRM. 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 CRM connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho CRM 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 CRM examples; they add no Zoho CRM capability - Zoho CRM is not an event source, a trigger cannot read Zoho CRM 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 let Maton access the selected Zoho CRM account. Prefer read-only OAuth scopes when possible, confirm every write or deletion, avoid raw API keys unless the CLI cannot be used, and treat hosted functions, triggers, destinations, and watch --exec as persistent automation that should be narrowly scoped and removed when no longer needed.
Capability Assessment
ℹ Credentials
Network access, OAuth, and a Maton account are proportionate for a CRM API integration; raw HTTP with MATON_API_KEY is documented only as a fallback when the CLI cannot be used, with credential-handling cautions.
✓ Install Mechanism
Installation is disclosed through pinned Maton CLI package commands and optional pinned SDK packages; no bundled executable files or hidden install scripts were present.
ℹ Instruction Scope
The skill includes broad CRM mutation examples and shared Maton trigger catalogues for other event sources, but repeatedly limits them to user-named tasks, least-privilege scopes, read-first behavior, and explicit approval for writes, functions, destinations, and local exec.
ℹ Persistence & Privilege
OAuth credentials, deployed functions, triggers, and destinations can persist, but the artifact discloses this, warns about ongoing forwarding and local exec risks, and requires user approval and cleanup.
✓ Purpose & Capability
The documented capabilities match the stated Zoho CRM purpose: read, create, update, delete, search CRM records, retrieve org/settings metadata, and optionally build user-approved Maton functions or triggers for automation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install zoho-crm
  3. After installation, invoke the skill by name or use /zoho-crm
  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.5
- Updated all base and endpoint URLs to use api.maton.ai instead of gateway.maton.ai or ctrl.maton.ai. - Removed LICENSE.txt file. - Added a Security & Permissions section, emphasizing the need for explicit user approval for write operations. - Clarified connection management steps and example headers for selecting among multiple accounts.
v1.0.4
- Expanded skill capabilities to include user management, organization settings, and module metadata retrieval in Zoho CRM. - Updated documentation to reflect support for accessing organization details and managing users. - Added references to retrieving module metadata alongside standard CRM data operations. - Cleaned up module descriptions and removed notes about additional OAuth scopes for core modules.
v1.0.3
- Added clawdbot metadata, including an emoji and required environment variable (MATON_API_KEY). - No functional or documentation changes to usage or API; only metadata updated.
v1.0.2
No changes detected in this version. - Version bumped to 1.0.2 with no file changes or content updates.
v1.0.1
No changes detected in this version. - No file changes were made between version 1.0.0 and 1.0.1.
v1.0.0
Initial release of Zoho CRM skill with managed OAuth integration. - Enables reading, creating, updating, and deleting Zoho CRM records (Leads, Contacts, Accounts, Deals, etc.) via API. - Includes full CRUD operations, bulk operations, and search for core modules. - Provides setup instructions for OAuth connections with Maton and API key management. - Supports multiple connections using custom headers. - Includes Python code examples for all key CRM operations.
Metadata
Slug zoho-crm
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 13
Frequently Asked Questions

What is Zoho CRM?

Zoho CRM API integration with managed OAuth. Manage leads, contacts, accounts, deals, and other CRM records. Use this skill when users want to read, create, update, or delete CRM records, search contacts, manage sales pipelines, access organization settings, manage users, or retrieve module metadata in Zoho CRM. 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 CRM connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho CRM 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 CRM examples; they add no Zoho CRM capability - Zoho CRM is not an event source, a trigger cannot read Zoho CRM 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 15046 downloads so far.

How do I install Zoho CRM?

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

Is Zoho CRM free?

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

Which platforms does Zoho CRM support?

Zoho CRM is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Zoho CRM?

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

💬 Comments