Git issue

Node catalog Actions
On this page

Creates an issue in a Git repository

Usage and specifics

The token must permit issue creation on the selected repository. title and body can use workflow data.

Technical type : git_issue. Runtime : nodulz.

Credentials and prerequisites

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter Type Default Values / limits
repo string "" -; min 1
credentialId string "" -; min 1
title string "" -; min 1
body string "" -

Configuration help

repo
Repository URL
HTTPS URL of a GitHub, GitLab or Gitea repository. Expressions supported.
credentialId
Git credential
Git credential with an HTTPS token and repository write access. Push also accepts an SSH key.
title
Title
Pull request or issue title. Expressions supported.
body
Body
Body or comment text. Expressions supported.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json
{
  "repo": "",
  "credentialId": "",
  "title": "",
  "body": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : Expressions and data, Executions, Node catalog.