corezoid-api-connector — Claude Code skill for Corezoid API
corezoid-api-connector — a skill for automating Corezoid operations through the public API. Builds processes that call /api/2/json/, work with nodes, processes, and tasks on the platform.
MIT ★ 74 updated 2026-10-29
/plugin marketplace add corezoid/corezoid-ai-plugin
/plugin install corezoid@corezoidWhat corezoid-api-connector does
This skill specializes in creating Corezoid processes that invoke the public API. When you tell the agent to call the Corezoid API or mention operations like fetching node lists, the skill activates and helps design an API Call node with the right configuration.
The skill includes a ready-made process pattern: Start → API Call → Reply Success → Done, with error and timeout handling. It generates the process JSON with correct settings — api_secret_outer for auth, stringified JSON in the ops field, empty format value. You provide three base params (api_login, api_secret, workspaceId) and operation-specific params like processId or limit.
Before generating, the skill reads corezoid-api-integration.md and checks openapi.corezoid.com to verify field names. After creation, it validates the process with lint-process, deploys it, and runs a smoke test.
What it helps with
- build a process that retrieves a list of nodes from Corezoid
- automate task data retrieval via the public API
- call an API operation with filtering and pagination
- handle errors and timeouts in API calls
- set up authentication using
api_secret_outer
Example prompts for the agent
- Create a process to fetch the node list with a limit of 50
- Call the Corezoid API to look up a process by ID
- Design an API Call node for
/api/2/json/with filters
How to install corezoid-api-connector
1Plugin marketplace
/plugin marketplace add corezoid/corezoid-ai-plugin/plugin install corezoid@corezoidThis installs the whole corezoid plugin with all its skills
2Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-api-connector -a claude-code3Manually: put the files in place
~/.claude/skills/corezoid-api-connector/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/corezoid-api-connector/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-api-connector -a codex2Manually: put the files in place
.agents/skills/corezoid-api-connector/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-api-connector -a cursor2Manually: put the files in place
.cursor/skills/corezoid-api-connector/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install corezoid/corezoid-ai-plugin plugins/corezoid/skills/corezoid-api-connector2Manually: put the files in place
.github/skills/corezoid-api-connector/SKILL.md1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill corezoid-api-connector -a gemini-cli2Platform CLI
gemini skills install https://github.com/corezoid/corezoid-ai-plugin --path plugins/corezoid/skills/corezoid-api-connectorManually: put the files in place
.devin/skills/corezoid-api-connector/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about corezoid-api-connector
How do I install corezoid-api-connector in Claude Code?
Run /plugin marketplace add corezoid/corezoid-ai-plugin, then /plugin install corezoid@corezoid. Next, npx skills add corezoid/corezoid-ai-plugin --skill corezoid-api-connector -a claude-code and open ~/.claude/skills/corezoid-api-connector/SKILL.md.
What does corezoid-api-connector do?
It helps the agent design a Corezoid process that calls the public API. It generates a ready-made process pattern with an API Call node, error handling, and authentication via api_secret_outer.
What parameters are required to use the API?
Three required: api_login (API key), api_secret (API secret used in api_secret_outer), and workspaceId (workspace ID). Plus operation-specific params — for example processId or limit for filtering.
Source text
SKILL.md · MIT
---
name: corezoid-api-connector
description: >
Corezoid API connector specialist. Use when the user wants to create a process
that calls the Corezoid public API (/api/2/json/), works with Corezoid objects
(nodes, processes, tasks, users) via the API, or needs to automate Corezoid
platform operations. Activate when the user says "call Corezoid API",
"Corezoid API connector", "node list", "api/2/json", "api_secret_outer",
or references openapi.corezoid.com operations.
---
# Corezoid API Connector
You are a specialist in building Corezoid processes that call the **Corezoid public API**.
> **Always read the reference doc before generating any JSON:**
> `${CLAUDE_PLUGIN_ROOT}/docs/process/corezoid-api-integration.md`
---
## Step 1: Identify the Operation
Ask the user:
- Which Corezoid API operation? (e.g. node list, process list, task list)
- What filtering/pagination params are needed? (limit, offset, obj_id, etc.)
- Where should the process be created? (folder path)
Check [openapi.corezoid.com](https://openapi.corezoid.com) for the `ops` fields of the target operation.
---
## Step 2: Create the Empty Process
Call **`create-process`** with:
- `process_name`: descriptive name, e.g. `"Corezoid API - Node List"`
- `folder_path`: target folder (omit for project root)
Check `scheme.nodes` in the created file — do not add a Start node if one already exists.
---
## Step 3: Define Input Parameters
Every Corezoid API connector requires these base params:
| Name | Type | Description |
| ------------- | ------ | ------------------------------------------- |
| `api_login` | string | API key login |
| `api_secret` | string | API key secret (used in `api_secret_outer`) |
| `workspaceId` | string | Workspace (company) ID |
Add operation-specific params (e.g. `processId`, `nodeId`, `limit`, `offset`).
---
## Step 4: Design the Process
### Process flow — no Code Node needed
```
Start → API Call → Reply Success → Done [obj_type:2]
│
(err)└──► Error Escalation [obj_type:3] ──► Error [obj_type:2]
(time)└─► Timeout Escalation [obj_type:3] ──► Timeout [obj_type:2]
```
### API Call node — key fields
```json
{
"type": "api",
"api_secret_outer": "{{api_secret}}",
"method": "POST",
"url": "https://api.corezoid.com/api/2/json/{{api_login}}",
"format": "",
"extra": {
"ops": "[{\"type\":\"<op_type>\",\"obj\":\"<obj>\",\"company_id\":\"{{workspaceId}}\", ...}]"
},
"extra_type": {
"ops": "array"
},
"extra_headers": { "content-type": "application/json; charset=utf-8" },
"send_sys": true,
"rfc_format": true,
"is_migrate": true,
"customize_response": false,
"response": { "body": "{{body}}", "header": "{{header}}" },
"response_type": { "body": "object", "header": "object" },
"version": 2,
"max_threads": 5,
"debug_info": false,
"cert_pem": "",
"err_node_id": "<error_escalation_id>"
}
```
Add a 30-second timeout semaphor to the API Call node.
### Reply Success node
```json
{
"type": "api_rpc_reply",
"mode": "key_value",
"res_data": { "result": "success", "response": "{{ops[0]}}" },
"res_data_type": { "result": "string", "response": "object" },
"throw_exception": false
}
```
### Critical rules
- `api_secret_outer` handles all authentication — **never** use a Code Node to compute SHA1
- `ops` value must be a **stringified JSON string**, type `"array"`
- `format` must be `""` (empty string) — not `"raw"`
- `send_sys: true` is required
- `customize_response: false` — use default `body`/`header` response mapping
---
## Step 5: Validate and Deploy
```
lint-process → fix errors → push-process → run-task (smoke test)
```
---
## Reference
| Resource | Path |
| ---------------- | ---------------------------------------------------------------- |
| Full pattern doc | `${CLAUDE_PLUGIN_ROOT}/docs/process/corezoid-api-integration.md` |
| Sample process | `${CLAUDE_PLUGIN_ROOT}/samples/corezoid-api-node-list.conv.json` |
| API reference | https://openapi.corezoid.com |
© Corezoid · MIT · corezoid/corezoid-ai-plugin