← Back to Skills Marketplace
byungkyu

zoho-inventory

by byungkyu · GitHub ↗ · v1.2.6 · MIT-0
cross-platform ✓ Security Clean
14423
Downloads
3
Stars
0
Active Installs
13
Versions
Install in OpenClaw
/install zoho-inventory
Description
Zoho Inventory API integration with managed OAuth. Manage items, sales orders, invoices, purchase orders, bills, contacts, and shipments. Use this skill when users want to read, create, update, or delete inventory items, sales orders, invoices, purchase orders, bills, or other inventory records in Zoho Inventory. 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 Inventory connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Inventory 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 Inventory examples; they add no Zoho Inventory capability - Zoho Inventory is not an event source, a trigger cannot read Zoho Inventory 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, be aware this skill can read and modify real Zoho Inventory business records and can set up persistent automations if you approve them. Use read-only scopes where possible, confirm every write or automation, and avoid third-party trigger destinations unless you understand exactly what data will be forwarded and for how long.
Capability Assessment
ℹ Credentials
Network access, Bash, and authenticated Maton/Zoho access are proportionate for an API integration, though users should expect access to inventory, orders, invoices, bills, contacts, and shipments within the connected account.
✓ Install Mechanism
Installation uses the Maton CLI through pinned npm or Homebrew instructions; no executable scripts are shipped in the artifact.
ℹ Instruction Scope
The package includes shared trigger references for non-Zoho event sources such as Calendly, but the main skill and reference files state these are platform catalogues only, do not widen Zoho Inventory access, and should be used only when the user asks for that source by name.
ℹ Persistence & Privilege
OAuth credentials, hosted functions, triggers, and trigger destinations can persist, but the skill discloses this and requires explicit approval, least-privilege scoping, DENY_ALL network policy by default for functions, and confirmation before writes or forwarding.
✓ Purpose & Capability
The stated purpose is Zoho Inventory CRUD and automation through Maton, and the documented API calls, connection handling, functions, and triggers align with that purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install zoho-inventory
  3. After installation, invoke the skill by name or use /zoho-inventory
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.6
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.5
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.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
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.2
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.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
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.4
- Updated all endpoint URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai. - Clarified connection management instructions and recommended always specifying the Maton-Connection header when multiple connections are active. - Added a new "Security & Permissions" section highlighting user approval requirements for write operations. - Removed LICENSE.txt file from the repository.
v1.0.3
- Added clawdbot metadata indicating required environment variable MATON_API_KEY. - No functional or documentation changes to the skill features. - Version number remains unchanged.
v1.0.2
- No file changes detected in this release. - Skill version bumped to 1.0.2; functionality and documentation remain unchanged.
v1.0.1
No user-facing changes in this version. - No file changes detected between versions. - Existing functionality and documentation remain unchanged.
v1.0.0
Initial release of Zoho Inventory skill with managed OAuth via Maton. - Enables full CRUD operations for items, sales orders, invoices, purchase orders, bills, contacts, shipment orders, and item groups via the Zoho Inventory API. - Managed authentication with Maton API key; supports multiple Zoho Inventory OAuth connections. - Provides base URL, quickstart scripts, and Python usage examples for API and connection management. - Includes support for specifying active connection using a header for multi-account scenarios. - Detailed documentation for key modules and endpoint usage.
Metadata
Slug zoho-inventory
Version 1.2.6
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 13
Frequently Asked Questions

What is zoho-inventory?

Zoho Inventory API integration with managed OAuth. Manage items, sales orders, invoices, purchase orders, bills, contacts, and shipments. Use this skill when users want to read, create, update, or delete inventory items, sales orders, invoices, purchase orders, bills, or other inventory records in Zoho Inventory. 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 Inventory connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Inventory 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 Inventory examples; they add no Zoho Inventory capability - Zoho Inventory is not an event source, a trigger cannot read Zoho Inventory 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 14423 downloads so far.

How do I install zoho-inventory?

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

Is zoho-inventory free?

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

Which platforms does zoho-inventory support?

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

Who created zoho-inventory?

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

💬 Comments