← CorezoidCONTENT HISTORY

Update to Corezoid

Snapshot Oct 9, 2026 · 00:04 UTC · version 3.9.0

Collection source: downloaded plugin package.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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.\n",
  "included_files": [],
  "name": "corezoid-api-connector",
  "skill_md_contents": "---\nname: corezoid-api-connector\ndescription: >\n  Corezoid API connector specialist. Use when the user wants to create a process\n  that calls the Corezoid public API (/api/2/json/), works with Corezoid objects\n  (nodes, processes, tasks, users) via the API, or needs to automate Corezoid\n  platform operations. Activate when the user says \"call Corezoid API\",\n  \"Corezoid API connector\", \"node list\", \"api/2/json\", \"api_secret_outer\",\n  or references openapi.corezoid.com operations.\n---\n\n# Corezoid API Connector\n\nYou are a specialist in building Corezoid processes that call the **Corezoid public API**.\n\n> **Always read the reference doc before generating any JSON:**\n> `${CLAUDE_PLUGIN_ROOT}/docs/process/corezoid-api-integration.md`\n\n---\n\n## Step 1: Identify the Operation\n\nAsk the user:\n\n- Which Corezoid API operation? (e.g. node list, process list, task list)\n- What filtering/pagination params are needed? (limit, offset, obj_id, etc.)\n- Where should the process be created? (folder path)\n\nCheck [openapi.corezoid.com](https://openapi.corezoid.com) for the `ops` fields of the target operation.\n\n---\n\n## Step 2: Create the Empty Process\n\nCall **`create-process`** with:\n\n- `process_name`: descriptive name, e.g. `\"Corezoid API - Node List\"`\n- `folder_path`: target folder (omit for project root)\n\nCheck `scheme.nodes` in the created file — do not add a Start node if one already exists.\n\n---\n\n## Step 3: Define Input Parameters\n\nEvery Corezoid API connector requires these base params:\n\n| Name          | Type   | Description                                 |\n| ------------- | ------ | ------------------------------------------- |\n| `api_login`   | string | API key login                               |\n| `api_secret`  | string | API key secret (used in `api_secret_outer`) |\n| `workspaceId` | string | Workspace (company) ID                      |\n\nAdd operation-specific params (e.g. `processId`, `nodeId`, `limit`, `offset`).\n\n---\n\n## Step 4: Design the Process\n\n### Process flow — no Code Node needed\n\n```\nStart → API Call → Reply Success → Done [obj_type:2]\n              │\n         (err)└──► Error Escalation [obj_type:3] ──► Error [obj_type:2]\n         (time)└─► Timeout Escalation [obj_type:3] ──► Timeout [obj_type:2]\n```\n\n### API Call node — key fields\n\n```json\n{\n  \"type\": \"api\",\n  \"api_secret_outer\": \"{{api_secret}}\",\n  \"method\": \"POST\",\n  \"url\": \"https://api.corezoid.com/api/2/json/{{api_login}}\",\n  \"format\": \"\",\n  \"extra\": {\n    \"ops\": \"[{\\\"type\\\":\\\"<op_type>\\\",\\\"obj\\\":\\\"<obj>\\\",\\\"company_id\\\":\\\"{{workspaceId}}\\\", ...}]\"\n  },\n  \"extra_type\": {\n    \"ops\": \"array\"\n  },\n  \"extra_headers\": { \"content-type\": \"application/json; charset=utf-8\" },\n  \"send_sys\": true,\n  \"rfc_format\": true,\n  \"is_migrate\": true,\n  \"customize_response\": false,\n  \"response\": { \"body\": \"{{body}}\", \"header\": \"{{header}}\" },\n  \"response_type\": { \"body\": \"object\", \"header\": \"object\" },\n  \"version\": 2,\n  \"max_threads\": 5,\n  \"debug_info\": false,\n  \"cert_pem\": \"\",\n  \"err_node_id\": \"<error_escalation_id>\"\n}\n```\n\nAdd a 30-second timeout semaphor to the API Call node.\n\n### Reply Success node\n\n```json\n{\n  \"type\": \"api_rpc_reply\",\n  \"mode\": \"key_value\",\n  \"res_data\": { \"result\": \"success\", \"response\": \"{{ops[0]}}\" },\n  \"res_data_type\": { \"result\": \"string\", \"response\": \"object\" },\n  \"throw_exception\": false\n}\n```\n\n### Critical rules\n\n- `api_secret_outer` handles all authentication — **never** use a Code Node to compute SHA1\n- `ops` value must be a **stringified JSON string**, type `\"array\"`\n- `format` must be `\"\"` (empty string) — not `\"raw\"`\n- `send_sys: true` is required\n- `customize_response: false` — use default `body`/`header` response mapping\n\n---\n\n## Step 5: Validate and Deploy\n\n```\nlint-process → fix errors → push-process → run-task (smoke test)\n```\n\n---\n\n## Reference\n\n| Resource         | Path                                                             |\n| ---------------- | ---------------------------------------------------------------- |\n| Full pattern doc | `${CLAUDE_PLUGIN_ROOT}/docs/process/corezoid-api-integration.md` |\n| Sample process   | `${CLAUDE_PLUGIN_ROOT}/samples/corezoid-api-node-list.conv.json` |\n| API reference    | https://openapi.corezoid.com                                     |\n"
}

SHA-256 of public snapshot: 42765293dc14204d7439e62d76ee6df36adb2127c1a453ee0c6c7c88d3848b3e