Create a runner group

Create a runner group: the repositories (by name) that may use the runners in it; empty for every repository.

POST/workspaces/{workspace}/actions/runner-groups

Owners only.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: workflow with action create_runner_group, and the same inputs
Scope: An access token needs runners:admin.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.

Body parameters

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name	Type	Required	Description
`id`	string	No	The group to change, from a list. Left out: a new group.
`name`	string	Yes	What to call it.
`repositories`	array of strings	No	Repository names that may use its runners. Empty is every repository in the workspace.

Example request

curl -X POST https://api.g1t.sh/workspaces/flagon-io/actions/runner-groups \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "GPU",
    "repositories": [
      "hello",
      "models"
    ]
  }'

Example response

A successful request answers 200 with:

{
  "id": "rng_01kq2m7r2a5d8g1j4m7p0s3v6z",
  "name": "GPU",
  "default": false,
  "repositories": [
    "hello",
    "models"
  ],
  "runners": 1,
  "updated_at": "2026-10-05T11:20:00.000Z"
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.