Zoho Crm
Wire your coding agent to Zoho CRM so you can create and sync leads, contacts, deals, and tasks without hand-rolling OAuth and API v6 plumbing.
Overview
Zoho CRM is an agent skill for the Build phase that connects your agent to Zoho CRM records and workflows through the Membrane CLI.
Install
npx skills add https://github.com/membranedev/application-skills --skill zoho-crmWhat is this skill?
- Authenticates Zoho CRM through Membrane with automatic credential refresh
- Covers core CRM objects: Leads, Contacts, Accounts, Deals, Tasks, Meetings, Calls, Modules, and Layouts
- Install via `npm install -g @membranehq/cli` and `membrane login` for tenant-scoped agent access
- Official Zoho CRM REST API v6 alignment with links in skill docs
- Free-tier Membrane account supported for indie builders prototyping CRM automation
- Documents 9 core Zoho CRM object areas including Leads, Contacts, Accounts, Deals, Tasks, Meetings, Calls, Modules, and
- Targets Zoho CRM REST API v6 per official developer documentation
Adoption & trust: 529 installs on skills.sh; 178 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need your agent to manage Zoho CRM leads, deals, and contacts but do not want to implement OAuth, token refresh, and API v6 requests yourself.
Who is it for?
Solo builders adding Zoho CRM read/write automation to an agent, internal tool, or early SaaS while using Membrane for auth.
Skip if: Teams that only need one-off CSV imports, already maintain a custom Zoho SDK in production, or cannot allow network access and third-party auth brokers.
When should I use this skill?
When the user wants to interact with Zoho CRM data—managing records, modules, layouts, or marketing and sales workflows via Membrane.
What do I get? / Deliverables
After setup, your agent can call Membrane-backed Zoho CRM operations with authenticated access so you can implement CRM automation in your app or workflow.
- Authenticated Membrane session scoped to Zoho CRM
- Agent-driven CRUD and workflow operations against Zoho CRM modules documented in the skill
Recommended Skills
Journey fit
Solo builders install this while building product features or internal tools that must read and write Zoho CRM records through a stable integration layer. The skill is a third-party SaaS connector (Membrane CLI + Zoho CRM API), which maps directly to the integrations shelf rather than pure backend business logic.
How it compares
Use this Membrane-packaged skill instead of pasting raw Zoho API keys and v6 curl examples into chat for every CRM task.
Common Questions / FAQ
Who is zoho-crm for?
It is for solo and indie developers who use AI coding agents to build or extend products that must talk to Zoho CRM for sales, marketing, or support data.
When should I use zoho-crm?
Use it during Build when wiring CRM integrations, and again in Grow or Operate when you want the agent to update pipeline records, tasks, or customer objects in a live Zoho tenant—any time the user wants to interact with Zoho CRM data.
Is zoho-crm safe to install?
The skill requires network access and routes authentication through Membrane; review the Security Audits panel on this Prism page and your Membrane tenant policies before connecting production CRM data.
SKILL.md
READMESKILL.md - Zoho Crm
# Zoho CRM Zoho CRM is a customer relationship management platform used by sales, marketing, and customer support teams. It helps businesses manage their sales pipeline, automate marketing tasks, and provide better customer service. Official docs: https://www.zoho.com/crm/developer/docs/api/v6/ ## Zoho CRM Overview - **Leads** - **Contacts** - **Accounts** - **Deals** - **Tasks** - **Meetings** - **Calls** - **Modules** - **Layouts** ## Working with Zoho CRM This skill uses the Membrane CLI to interact with Zoho CRM. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing. ### Install the CLI Install the Membrane CLI so you can run `membrane` from the terminal: ```bash npm install -g @membranehq/cli@latest ``` ### Authentication ```bash membrane login --tenant --clientName=<agentType> ``` This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available. **Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with: ```bash membrane login complete <code> ``` Add `--json` to any command for machine-readable JSON output. **Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness ### Connecting to Zoho CRM Use `membrane connection ensure` to find or create a connection by app URL or domain: ```bash membrane connection ensure "https://www.zoho.com/crm" --json ``` The user completes authentication in the browser. The output contains the new connection id. This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically. If the returned connection has `state: "READY"`, skip to **Step 2**. #### 1b. Wait for the connection to be ready If the connection is in `BUILDING` state, poll until it's ready: ```bash npx @membranehq/cli connection get <id> --wait --json ``` The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`. The resulting state tells you what to do next: - **`READY`** — connection is fully set up. Skip to **Step 2**. - **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action: - `clientAction.type` — the kind of action needed: - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections. - `"provide-input"` — more information is needed (e.g. which app to connect to). - `clientAction.description` — human-readable explanation of what's needed. - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present. - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically. After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`. - **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details. ### Searching for actions Search using a natural la