Corezoid

Move a Corezoid project to the recycle bin (Trash). It can be restored from the Corezoid UI; permanent destruction is only possible there.

delete-project

Delete a task from a process. At least one of task_id or ref must be provided. If only ref is given, the task_id and node_id are resolved automatically.

delete-task

Deploy (promote) one stage's processes onto another within a Corezoid project — e.g. develop → production. Wraps the admin obj_scheme compare+merge behind the UI's "Deploy" button (/api/2/compare, /api/2/merge). DESTRUCTIVE, and irreversible on an immutable target. SAFETY: apply=false (default) is a dry-run showing only the diff and any conflicts — nothing is deployed. To deploy you MUST first get the user's explicit confirmation of the exact source→target, then call with apply=true AND confirm="<source_stage_id>-><target_stage_id>". Never deploy without the user confirming. The merge is asynchronous; this tool waits for it to finish over the progress WebSocket.

deploy-stage

Search users, groups or API keys in the workspace by substring. Returns obj_ids to pass as obj_to_id in share-object.

find-principal

Get a single chart with its series data.

get-chart

Get a Corezoid dashboard with its charts and series. Use after add-chart to verify series is populated.

get-dashboard

Return time-series statistics (in/out counts) for a node over a time range. node_id is the ID shown in the Corezoid UI archive URL (/diagram/{node_id}/archive). ops[0]['data'] contains [{"date":"YYYY-MM-DD","in":N,"out":M}] for non-zero buckets. ops[0]['title'] is the node title.

get-node-stat

Invite an external email to the workspace AND share a process/folder/stage/project with them in one call. Returns the invite URL the recipient must open.

invite-user

Lint a Corezoid process given as JSON text: structural problems, unreachable or no-op nodes, missing error branches, literal values that should be env variables, schema validity. Runs locally on the content; calls nothing.

lint-process

List the aliases (short_name -> target process) defined in a Corezoid project's stage. Pass short_name to filter to one exact match instead of scanning the full table — the common case when resolving a known alias (e.g. a Smart API receiver) to its conv_id.

list-aliases

List API keys visible in the current workspace.

list-api-keys

List the immediate children of a Corezoid folder (subfolders, processes and state diagrams). Read-only.

list-folders

List the processes (conv objects) currently shared with a group. Used to audit group impact before destructive operations. Note: folders/stages/projects shared to the group are not retrievable via this endpoint.

list-group-objects

List user groups visible in the current workspace.

list-groups

Return tasks currently sitting in a specific node of a process. This is a paged scan of one node, not a lookup — to find one task by ref or task_id use show-task instead.

list-node-tasks

Return the list of projects inside a Corezoid workspace (company), sorted by title.

list-projects

List users, API keys and groups that currently have access to a Corezoid object.

list-shares

Return the list of stages (environments) inside a Corezoid project.

list-stages

Return the execution history (node path) for a task. Shows each node transition with node_id, node_prev_id, create_time_ms. NOTE: the Corezoid API does not record data snapshots — the data field is always null in history entries. To inspect the current data payload, use show-task (read-only); it also resolves the task_id this tool requires from a ref.

list-task-history

List the environment variables (env_var) of the stage given in scope.stage_id: short_name, obj_id, data_type (raw/json), env_var_type (visible/secret), title, value and change time. Read-only; secret variables are always shown masked.

list-variables

Return the list of Corezoid workspaces (companies) available to the authenticated user.

list-workspaces

Update title and/or description of an existing API key. Does not regenerate the secret.

modify-api-key

Modify an existing Corezoid chart. Always provide the full series array — partial updates are not supported.

modify-chart

Rename a Corezoid folder and/or update its description. At least one of title or description must be supplied.

modify-folder

Rename a user group and/or update its description. At least one of title or description must be supplied.

modify-group

Update a Corezoid project's title, short_name and/or description. At least one of title/short_name/description must be provided.

modify-project

Modify an existing task's data; at least one of task_id or ref is required. WARNING: the Corezoid API does a SHALLOW (top-level) merge — if a top-level key holds a nested object (e.g. data.currencies), its whole value is replaced and sub-keys absent from your payload are silently lost. Pass deep_merge: true to fetch current task data first and merge recursively, preserving sub-keys.

modify-task

Move (reparent) one existing NORMAL Corezoid folder to another folder in the configured workspace, preserving its folder ID and descendants; NOT copy, import, or deploy. Projects and stages are intentionally rejected. EXPLICIT-INTENT ONLY: never reorganize automatically during create/edit/review/refactor. SAFETY: apply=false (default) reads the live parent, destination and effective project/stage contexts, checks destination ancestry to prevent self/descendant cycles, and returns a dry-run; to apply, show it to the user and pass the exact context-bound confirm token it returned. Moving the source, destination or either effective stage/project context invalidates an old token; completion is post-verified. destination_folder_id=0 means workspace root. Cross-stage/project/root moves also require allow_cross_stage=true and affect every descendant's environment context. Local mirror directories are not relocated automatically.

move-folder

Move (reparent) one existing Corezoid process/state diagram to another folder in the configured workspace, preserving its object ID and graph; NOT copy, import, or deploy. EXPLICIT-INTENT ONLY: never reorganize objects automatically during create/edit/review/refactor — use only when the user names both object and destination. SAFETY: apply=false (default) reads the live current parent, destination and effective project/stage contexts and returns a dry-run; to apply, show it to the user and pass the exact context-bound confirm token it returned. Moving the source, destination or either effective stage/project context invalidates an old token; completion is post-verified. destination_folder_id=0 means workspace root. Cross-stage/project/root moves also require allow_cross_stage=true, because stage-scoped aliases/variables, access and deployment behavior are not migrated. Local mirror files are not relocated automatically.

move-process

Pause one Corezoid process without changing or deploying its graph. CONSEQUENTIAL: Corezoid rejects NEW task creation for a paused process with conveyor_is_not_active — that is admission control, not proof that tasks already running or parked in nodes have stopped; inspect those separately. EXPLICIT-INTENT ONLY: never invoke because a process looks unused, during a review/refactor, or as an inferred safety step — only when the user asks to pause this exact process. SAFETY: apply=false (default) reads live status and returns a dry-run; after showing it and receiving explicit approval, call apply=true with confirm="process#<id>:<live_status>->paused". The live status is re-read on every invocation and the result is post-verified.

pause-process

Fetch a Corezoid process as JSON. Returns the process scheme and a `base` token naming the server version it was read at — keep it: a later deploy of this process compares it with the server to detect concurrent changes. Read-only; nothing is written anywhere.

pull-process

Validate and deploy a Corezoid process from JSON. Runs the same gates as the local push: structure fix, schema, lint (force=true overrides blocking findings, never structural ones), a concurrency check against `base`, a pre-push snapshot, and the irreversibility check. Pass the `base` token from pull-process / create-process: if someone changed the process on the server since, the push is blocked with a report — pull again and re-apply your edits (merging is not available on the hosted server). Needs scope.stage_id for the snapshot. Returns the deployed scheme with the server's node IDs and a new `base` for the next edit.

push-process

Remove a user from a group.

remove-from-group

Resume (activate) one paused/debug Corezoid process without changing or deploying its graph. CONSEQUENTIAL: after activation, API clients, schedules, callbacks and other processes may create new tasks immediately. EXPLICIT-INTENT ONLY: never resume automatically after edits, tests, a review or a previous pause — only when the user asks to resume this exact process and accepts incoming traffic. SAFETY: apply=false (default) reads live status and returns a dry-run; after showing it and receiving explicit approval, call apply=true with confirm="process#<id>:<live_status>->active". The live status is re-read on every invocation and the result is post-verified.

resume-process

Create a task in a deployed Corezoid process and wait for it to reach a final node. Returns the task's final node and data.

run-task

Save chart positions on a dashboard grid. Must be called after add-chart/modify-chart to make charts visible. Each grid entry positions one chart by its chart_id (hex string from add-chart).

set-dashboard-layout

Set a stage's immutable (read-only) flag. Immutable stages are the ONLY valid deploy/merge targets (see deploy-stage); an immutable stage can no longer be edited directly — only changed via deploy. Consequential: making a stage editable removes that protection. Requires explicit user confirmation — call with confirm="<stage_id>:<true|false>" (e.g. "684082:true"). Never change immutability without the user confirming.

set-stage-immutable

Grant or revoke access to a Corezoid object (process/folder/stage/project) for a user, API key, or group. To revoke, pass privs="none" — that's the same wire operation as a share with empty privs. API keys share as obj_to="user" with the api key's obj_id.

share-object

Show metadata for a single Corezoid folder: title, obj_type (0 normal, 2 project, 3 stage), parent folder ID and parent type.

show-folder

Show a Corezoid process's own metadata (title, description, status, conv_type, owner_id/owner_login, project_id, stage_id, immutable) without exporting its scheme. Lighter than pull-process for an ownership/location lookup.

show-process