---
title: "corestack_enterprise_deployment_trigger"
url: https://docs.corefinity.com/mcp/tools/corestack_enterprise_deployment_trigger
type: tool
last_updated: 2026-11-13
feature: enterprise-deployments
related:
  - https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md
---
# corestack_enterprise_deployment_trigger

**Deploy on a CoreStack Enterprise environment.** Deploy on a CoreStack Enterprise environment: start a waiting deployment, or deploy a commit of one of its repositories. Scope: write. Long-running: answers with a task.

- Scope: `write`
- Runs as a task: yes

## When to use it

Deploy on a CoreStack Enterprise environment, one of two ways:

- **Start a waiting deployment** (`deployment_id`): an environment that deploys git pushes by hand keeps each push
  waiting (`pending`) until someone presses Deploy. This is that button: the deployment is built from its pipeline as it
  is now, or on another pipeline of the environment (`pipeline_id`).
- **Deploy a commit** (`repository_id` + `commit`): a new deployment of that commit of one of the environment's
  repositories, through the pipeline the repository deploys with.

A task follows the deployment to its end; poll it, or read `corestack_enterprise_deployment_get`. Cancelling the task
cancels the deployment. Uploading a release archive is the public API's `POST /api/environments/{environment}/deployments`
(a file body); the same two ways are its `POST …/deployments/{deployment}/run` and the same `POST` with `git`.

## Inputs

- `enterprise_env_id` (integer, ≥ 1, required)
- `deployment_id` (integer, ≥ 1): a waiting deployment to start
- `pipeline_id` (integer, ≥ 1): with `deployment_id` only, another pipeline of the environment to start it on
- `repository_id` (integer, ≥ 1): with `commit`, a new deployment of that repository of the environment
- `commit` (string, a full 40- or 64-character hexadecimal SHA): with `repository_id`
- `name` (string, ≤ 255): with a commit only
- `notes` (string, ≤ 10000): with a commit only

Give `deployment_id`, or `repository_id` and `commit`: never both, never neither.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "commit": {
      "description": "A full commit SHA of repository_id.",
      "pattern": "^(?:[a-fA-F0-9]{40}|[a-fA-F0-9]{64})$",
      "type": "string"
    },
    "deployment_id": {
      "description": "A waiting deployment to start.",
      "minimum": 1,
      "type": "integer"
    },
    "enterprise_env_id": {
      "description": "A CoreStack Enterprise environment's id; for CoreStack or CoreCluster use the corestack_deployment_* tools.",
      "minimum": 1,
      "type": "integer"
    },
    "name": {
      "maxLength": 255,
      "type": "string"
    },
    "notes": {
      "maxLength": 10000,
      "type": "string"
    },
    "pipeline_id": {
      "minimum": 1,
      "type": "integer"
    },
    "repository_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "enterprise_env_id"
  ],
  "type": "object"
}
```

## Refusals

- `invalid_arguments`: neither or both ways given, `pipeline_id` with a commit, a commit that is not a full SHA, or a
  repository that is not this environment's (field `repository_id`); a CoreStack or CoreCluster environment (field
  `enterprise_env_id`).
- `stale`: that deployment is not waiting any more, or the environment has already moved past it, or the pipeline
  chosen — for a commit, the pipeline its repository deploys with — is no longer available in the environment. Read it
  again.
- `busy`: the same start is still being applied. `forbidden`: the person's role lacks the Create Deployments permission
  (Deploy Deployments to start a waiting deployment). The message names it and says an owner of the company can grant it
  in Roles; `details.permission` is `createDeployments` (or `deployDeployments`).
- `no_namespace` (`panel_status` 409): the environment has no namespace on its cluster, so there is nothing to deploy to.
  Nothing is created; the Control Panel's Deploy form and the REST API refuse it in the same words. Staff must look at the
  environment.
- `tenant_mismatch`, `pin_refused`, and the refusals every tool can answer: `scope_required`, `rate_limited`,
  `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_enterprise_deployment_trigger",
  "arguments": {
    "enterprise_env_id": 1530,
    "repository_id": 812,
    "commit": "4f2c9a1e0b7d3c5a6e8f9b0c1d2e3f4a5b6c7d8e",
    "notes": "Hotfix for the checkout page"
  }
}
```

Starting a waiting deployment:

```json
{
  "name": "corestack_enterprise_deployment_trigger",
  "arguments": {
    "enterprise_env_id": 1530,
    "deployment_id": 185190
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_enterprise_deployment_trigger with enterprise_env_id 1530, repository_id 812, commit 4f2c9a1e0b7d3c5a6e8f9b0c1d2e3f4a5b6c7d8e, notes Hotfix for the checkout page. (Deploy on a CoreStack Enterprise environment.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [Deployments and pipelines](https://docs.corefinity.com/guides/corestack-enterprise/deployments-and-pipelines.md)
