Delete Repository

github.delete_repo
ActionBusiness appsconnection required

Calls the GitHub API DELETE /repos/{owner}/{repo}.

Permanently delete a repository, after confirming its full name.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
GitHub
Secret shape
the GitHub personal access token
Resolved by
config.connection_id, else node.connection_id, else the tenant's sole GitHub connection

Configuration

3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
owner
Repository owner — the user or organisation login. Supports {{ }}.
stringYes——octocat
repo
Repository name, without the owner prefix. Supports {{ }}.
stringYes——hello-world
confirm
Type the exact owner/repo being deleted; the step refuses to call otherwise.
stringYes———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "owner": "octocat",
  "repo": "hello-world"
}

Output

One shape.

result

FieldTypeExample
ok
True when GitHub accepted the call.
booleantrue
full_name
The repository that was deleted.
string—
{
  "full_name": "",
  "ok": true
}

Notes

  • Irreversible: GitHub does not undo this from the API.
  • The token needs the delete_repo scope, which fine-grained tokens grant separately.

See Delete Repository run in a workflow.

In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.