← Back to Skills Marketplace
byungkyu

zoho-recruit

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
14231
Downloads
3
Stars
0
Active Installs
14
Versions
Install in OpenClaw
/install zoho-recruit
Description
Zoho Recruit API integration with managed OAuth. Manage candidates, job openings, interviews, and recruitment workflows. Use this skill when users want to read, create, update, or search recruitment data like candidates, job openings, interviews, and applications in Zoho Recruit. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI after `maton login`; the Zoho Recruit credential stays in the gateway and is never handled locally. Default to read and list calls, and confirm every write or new connection with the user. Deletions are bulk and irreversible - approve each record individually. This file also documents the three constructs that turn a Zoho Recruit connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Recruit 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 Recruit examples; they add no Zoho Recruit capability - Zoho Recruit is not an event source, a trigger cannot read Zoho Recruit 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 trust Maton with Zoho Recruit access. Use the narrowest Zoho OAuth scopes available, confirm the exact account/connection before writes, review every deletion record-by-record, and avoid trigger destinations or hosted functions unless you deliberately want ongoing automation and understand what data will flow where.
Capability Assessment
ℹ Credentials
The skill handles sensitive recruiting data and can use a generic gateway path under /zoho-recruit/, so users should keep scopes narrow; the artifact discloses this and gives least-privilege and endpoint-boundary guidance.
ℹ Install Mechanism
Installation requires the Maton CLI via pinned npm or Homebrew instructions plus network access and a Maton account; this is coherent for a managed OAuth gateway, with no bundled executable scripts in the artifact.
✓ Instruction Scope
The skill repeatedly scopes behavior to documented Zoho Recruit paths, defaults to read/list actions, requires explicit approval for connection creation, writes, deletes, hosted functions, trigger destinations, and local --exec usage, and treats returned content as untrusted data.
ℹ Persistence & Privilege
OAuth tokens are stored in the OS credential store by the CLI, and optional triggers/destinations/functions can create persistent automation or forwarding, but these behaviors are explicitly documented and gated by user approval guidance.
✓ Purpose & Capability
The stated purpose is Zoho Recruit API access for recruiting records, and the documented capabilities match that purpose: read, create, update, delete, search, and optional Maton-hosted functions/triggers for user-approved automation.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install zoho-recruit
  3. After installation, invoke the skill by name or use /zoho-recruit
  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.2
- Removed the file skill-card.md. - No changes to functionality or behavior; documentation and code remain the same.
v1.1.1
- Removed the file skill-card.md. - Updated documentation to clarify that credentials are handled only in the gateway and never surface locally. - Added stronger guidance and controls on endpoint usage and bulk deletions. - Expanded security, review, and usage instructions for API calls to Zoho Recruit.
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
- Changed all API and connection management URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai. - Clarified connection management instructions and response JSON to use generic `{connection_id}` placeholders. - Added a Security & Permissions section emphasizing that all write operations require explicit user approval. - Updated connection header usage guidance: always include `Maton-Connection` if you have multiple connections. - Removed legacy references and unused LICENSE.txt for cleaner distribution.
v1.0.3
- Added clawdbot metadata, including an emoji and required environment variable details, to the skill configuration. - No changes to skill logic or API usage.
v1.0.2
- No file changes detected in this version. - Functionality, documentation, and metadata remain the same as previous release.
v1.0.1
No code or documentation changes detected in this release. - Version bumped from 1.0 to 1.0.1 with no content changes. - No new features, fixes, or documentation updates.
v1.0.0
Initial release of Zoho Recruit API skill. - Integrates Zoho Recruit API via managed OAuth authentication. - Supports full CRUD operations for candidates, job openings, interviews, applications, and more. - Provides detailed setup instructions for API key and OAuth connection management. - Includes ready-to-use Python code samples for common operations. - Offers guidance for specifying active connections when managing multiple Zoho Recruit accounts.
Metadata
Slug zoho-recruit
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 14
Frequently Asked Questions

What is zoho-recruit?

Zoho Recruit API integration with managed OAuth. Manage candidates, job openings, interviews, and recruitment workflows. Use this skill when users want to read, create, update, or search recruitment data like candidates, job openings, interviews, and applications in Zoho Recruit. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI after `maton login`; the Zoho Recruit credential stays in the gateway and is never handled locally. Default to read and list calls, and confirm every write or new connection with the user. Deletions are bulk and irreversible - approve each record individually. This file also documents the three constructs that turn a Zoho Recruit connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Recruit 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 Recruit examples; they add no Zoho Recruit capability - Zoho Recruit is not an event source, a trigger cannot read Zoho Recruit 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 14231 downloads so far.

How do I install zoho-recruit?

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

Is zoho-recruit free?

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

Which platforms does zoho-recruit support?

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

Who created zoho-recruit?

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

💬 Comments