corezoid-alias-manager

Corezoid Alias Manager

What aliases are

An alias is a human-readable short_name (e.g. payment-service, send-otp) that maps to a process (conv). Aliases serve two purposes:

1. Process reference in JSON — use @alias-name as conv_id instead of a numeric process ID. This makes processes portable across environments and removes hardcoded IDs.
2. External HTTP entry point — each alias generates a callback_hash used to send tasks to the process via the API Gateway URL.

Alias naming rules (same as Corezoid short names):

• Only lowercase letters [a-z], digits [0-9], and hyphens -
• Must be at least 3 characters
• Must be unique within the stage
• Good: payment-checkout, send-otp, create-user-v2
• Bad: MyAlias, PAYMENT, a

---

MCP Tools

Tool	Purpose
create-alias	Create an alias and link it to a process in one step

Note: list, modify, delete, and unlink operations are not yet exposed as MCP tools. Use the direct API calls documented below to perform them.

---

Using aliases in process JSON

Once an alias exists, replace the numeric conv_id with @alias-name in any node that calls another process:

Call a Process node (api_rpc)

{
  "type": "api_rpc",
  "conv_id": "@payment-checkout",
  "extra": { "amount": "{{amount}}", "currency": "{{currency}}" },
  "extra_type": { "amount": "number", "currency": "string" },
  "err_node_id": "<error_node_id>"
}

Copy Task node (api_copy)

{
  "type": "api_copy",
  "conv_id": "@send-notification",
  "ref": "{{unique_ref}}",
  "mode": "create",
  "err_node_id": "<error_node_id>"
}

State store read in set_param or condition

{{conv[@user-states].ref[{{task_ref}}].status}}

This reads the status field of the task with reference {{task_ref}} from the @user-states state diagram process.

---

Workflow: Create an alias

Step 1 — Resolve the process

Check whether the user provided a file path, process name, or process ID. If a file path is given, the process ID is the leading number in the filename (e.g. 1834583_My_Process.conv.json → process_id = 1834583).