← 返回 Skills 市场
byungkyu

zoho-bigin

作者 byungkyu · GitHub ↗ · v1.2.6 · MIT-0
cross-platform ✓ 安全检测通过
14058
总下载
4
收藏
0
当前安装
13
版本数
在 OpenClaw 中安装
/install zoho-bigin
功能描述
Zoho Bigin API integration with managed OAuth. Manage contacts, companies, pipelines, and products in Bigin CRM. Use this skill when users want to read, create, update, or delete CRM records, search contacts, or manage sales pipelines. 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 Bigin connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Bigin 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 Bigin examples; they add no Zoho Bigin capability - Zoho Bigin is not an event source, a trigger cannot read Zoho Bigin 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).
安全使用建议
Before installing, understand that this skill can read and modify Zoho Bigin CRM data through your Maton connection. Use OAuth when possible, approve every write or automation explicitly, avoid broad OAuth scopes, and be especially cautious with persistent triggers or third-party destinations because they can continue forwarding event data until removed.
能力评估
✓ Credentials
Network access, OAuth, and CRM record permissions are expected for a Zoho Bigin integration. The artifact instructs users to use least privilege, prefer OAuth, avoid credential inspection, and limit raw API-key use to environments without the CLI.
ℹ Install Mechanism
Installation uses a pinned global Maton CLI package or Maton's Homebrew tap, with optional pinned SDKs. No executable files are shipped in the skill artifact itself.
✓ Instruction Scope
Instructions default to read/list operations, require explicit user approval for writes, new connections, function deployment, trigger destinations, and local event execution, and warn that third-party API content is untrusted data.
ℹ Persistence & Privilege
The skill documents persistent hosted functions, triggers, destinations, and event watches, but it clearly frames them as non-default automation requiring separate approval, DENY_ALL network policy by default, user-reviewed code, and cleanup when no longer needed.
ℹ Purpose & Capability
The skill's purpose is coherent with CRM API access through Maton. Its API reference is broader than the headline examples because it also documents Tasks, Events, Calls, Notes, Users, and custom modules, but those are visible in the artifact and are CRM-adjacent rather than hidden.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install zoho-bigin
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /zoho-bigin 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
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
- Switched all API and connection management URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai. - Updated code examples and documentation to use the new api.maton.ai endpoint format. - Reworded connection specification instructions for clarity; the `Maton-Connection` header usage is now strongly recommended when multiple accounts are present. - Added a "Security & Permissions" section with guidelines for write operations, emphasizing explicit user approval for changes. - Removed the LICENSE.txt file.
v1.0.3
- Added skill metadata for Clawdbot, including an emoji and required environment variable information. - The MATON_API_KEY environment variable is now explicitly documented as a requirement in metadata. - No functional or documentation changes to the Zoho Bigin integration itself.
v1.0.2
Version 1.0.2 of the Zoho Bigin skill - No code or documentation changes detected for this release. - All features and instructions remain the same as the previous version.
v1.0.1
No changes detected from the previous version. - Version bump to 1.0.1 with no file or documentation changes.
v1.0.0
Initial release of Zoho Bigin API integration: - Full CRUD support for contacts, companies (accounts), pipelines, products, and more via Zoho Bigin API. - Managed OAuth authentication; easily connect/manage authorized accounts through Maton control panel. - Maton API key required for all requests. - Supports multiple connections with header-based selection. - Example Python snippets provided for all major operations.
元数据
Slug zoho-bigin
版本 1.2.6
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 13
常见问题

zoho-bigin 是什么?

Zoho Bigin API integration with managed OAuth. Manage contacts, companies, pipelines, and products in Bigin CRM. Use this skill when users want to read, create, update, or delete CRM records, search contacts, or manage sales pipelines. 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 Bigin connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Zoho Bigin 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 Bigin examples; they add no Zoho Bigin capability - Zoho Bigin is not an event source, a trigger cannot read Zoho Bigin 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). 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 14058 次。

如何安装 zoho-bigin?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install zoho-bigin」即可一键安装,无需额外配置。

zoho-bigin 是免费的吗?

是的,zoho-bigin 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

zoho-bigin 支持哪些平台?

zoho-bigin 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 zoho-bigin?

由 byungkyu(@byungkyu)开发并维护,当前版本 v1.2.6。

💬 留言讨论