Skip to main content

Documentation index: llms.txt. This page is also available as markdown: append .md to this URL or send Accept: text/markdown.

What's My ID?

Coalesce APIs, the CLI (COA), and Transform MCP often require numeric or string IDs for Environments, Projects, Workspaces, Nodes, Jobs, and runs. This page shows where to find each ID in the app and which format each integration expects.

For Transform MCP tool names that use each ID, see the ID type table below and Available Tools.

ID Types at a Glance​

IDFormatCommon uses
Environment IDStringREST and MCP environment and node reads; runs_start, runs_cancel
Project IDStringREST and MCP project reads; environments_create; runs_list filters
Workspace IDStringREST workspace nodes; nodes_list_workspace, nodes_get_workspace
Node IDStringREST and MCP node reads
Run IDIntegerREST run reads; MCP runs_get, runs_results, runs_retry, runs_cancel, runs_status
Job IDStringMCP runs_start when scoping to a Job
Org IDStringSupport and account context
Run ID is numeric, not a URL UUID

The scheduler API names the numeric run identifier runCounter. Transform MCP tools expose it as runID. A run URL may contain a UUID, but that UUID is not the run ID REST or MCP tools accept.

Environment ID​

In the app:

  • Go to Build Settings > Environments.

    Environments section under Build Settings in a Coalesce interface. It lists two environments, Production with ID 2 and QA with ID 6, along with a button to create a new environment.

  • On the Deploy page, select an Environment. The ID appears in the URL or Environment details.

    Deployment history for the environments Production and QA. The Production environment, with ID 2, has a failed deploy status, while the QA environment, with ID 6, has an OK status, indicating successful deployments

Via API or Transform MCP:

  • Call List Environments or the environments_list MCP tool and read the id field from the response.

Project ID​

In the app:

  • On the Deploy page, filter by Project and read the ID from the browser URL.

    A screenshot of the Coalesce application's user interface. Red boxes highlight the unique project ID in the browser's address bar and the project selection dropdown menu on the left side of the page.

Via API or Transform MCP:

  • Call List Projects or the projects_list MCP tool and read the id field from the response.

Workspace ID​

In the app:

  • Go to Build Settings > Workspaces.

    Workspace section under Build Settings in a Coalesce interface. It lists the Development workspace with ID 1.

Via API or Transform MCP:

  • Call List Projects with the includeWorkspaces query parameter, or call projects_get with includeWorkspaces: true, and read Workspace IDs from the nested response.

Node ID​

In the app:

  • In the Node editor for the Node you are editing.

    STG_CUSTOMER node in the Build Settings section, showing various column attributes like name, transform, data type, and source, with a message indicating the node is not enabled for deployment. The node ID is highlighted as 13471f9f-a043-4983-84eb-069db056cf91

  • In run results for an Environment.

    Deployment results for Run ID 17 in the QA environment. The STG_CUSTOMER node with the same node ID 13471f9f-a043-4983-84eb-069db056cf91 has completed successfully, with details like job name, start and end times, and stage status

Via API or Transform MCP:

  • Call List Nodes with an Environment ID, or nodes_list_environment / nodes_list_workspace for MCP.
  • Call List Run Results for a run.

Run ID​

In the app:

  • Open run results for an Environment on the Deploy page. The numeric run counter appears in run details.

    Deployment details for Run ID 17, summarizing the job name, type, triggered by, start and end times, and duration. The successful completion of the deployment is highlighted, with the same node ID for STG_CUSTOMER indicated

Via API or Transform MCP:

  • Call List Runs or the runs_list MCP tool. Use the numeric run identifier from each run object, not the UUID in the browser URL.
# Correct for runs_get, runs_status, and similar tools
runID: 42

# Wrong — UUID from a run URL is not runID
runID: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"

Job ID​

To scope a refresh run to a Job (REST Start Run or MCP runs_start):

  • Open Deploy and select an Environment.

Or call projects_get with includeJobs: true and read Job IDs from the nested Workspace data.

Org ID​

  • Open your user profile in Coalesce and click Support Information.

    The Coalesce support information screen

Tips for Transform MCP​

When prompting an AI assistant to call Transform MCP tools:

  • Ask it to call projects_list or environments_list first if you do not know the IDs.
  • For run operations, say "use the numeric run counter" if the assistant passes a UUID from a URL.
  • For full-environment refreshes, the assistant must pass a jobID or includeNodesSelector, or set confirmRunAllNodes: true.

What's Next?​