corestack_ deployments_ company_ variable_ set
Set a company deployment variable.
When to use it
Create or change one of your company's deployment variables, which its sites' three-stage environments receive as CF_<name> when their deployments are built, unless an environment sets the name itself. Send value, shared_with_managed or both; a new name needs a value. shared_with_managed matters only for an agency: the value then also reaches the builds of the sites it manages for clients, whose users can run commands there. The value is write-only: it is never shown again here. A token restricted to some sites cannot change company variables.
The same action in the public REST API, with the same checks, refusals and scope: PUT /.
Ask for it
Using the Corefinity MCP server, call corestack_deployments_company_variable_set with name SLACK_WEBHOOK, value <the webhook address>, shared_with_managed false. (Set a company deployment variable.) Tell me what it returned.Inputs
Without the CF_ prefix.
An agency only: also the sites it manages for clients.
Up to 2,048 characters.
Example call
{
"name": "corestack_deployments_company_variable_set",
"arguments": {
"name": "SLACK_WEBHOOK",
"value": "<the webhook address>",
"shared_with_managed": false
}
}If it is refused
| Reason | What to do |
|---|---|
forbidden | The person's role lacks the Edit Environment Deployment Pipeline permission, which every change to the company's templates, variables and registry secrets needs (they reach every environment that follows the template). The message names it and says an owner of the company can grant it in Roles; details.permission is editEnvironmentDeploymentPipeline. Nothing is changed. |
variable_reserved | That name is reserved for a value the platform sets. |
variable_tool_credential | A new variable named as a build tool's credential (COMPOSER_AUTH, NPM_TOKEN, NODE_AUTH_TOKEN, YARN_NPM_AUTH_TOKEN, GITHUB_TOKEN, GITLAB_TOKEN, BITBUCKET_TOKEN, in any case; details.field is name). Builds receive it as CF_<name>, so the tool never reads it. The message says so and points at Private registries; save the credentials with corestack_ instead. An existing one is kept and can still be changed or deleted. |
variable_invalid | The name starts with CF_, the value has a line break, a control character or is too long, or a new name was sent without a value. |
too_many_variables | The company already holds the most variables it can (100); delete one first. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |