Checkout

Node catalog Actions

On this page

Clones a repository into a shared run workspace for downstream nodes

Usage and specifics

The repository is cloned into a workspace shared by the run. Source it from the Git trigger, a project or an expression. Private repositories need a Git credential.

Technical type : checkout. Runtime : nodulz.

Credentials and prerequisites

Create and configure the credential : git

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
`source`	`union`	`{"kind":"from_trigger_git"}`	-
`source.kind`	`literal`	`"from_trigger_git"`	`from_trigger_git`, `from_project`, `manual`, `from_expression`
`source.credentialId`	`string`	-	-
`source.projectId`	`string`	-	-; min 1
`source.ref`	`string`	-	-
`source.repo`	`string`	-	-; min 1

Examples

Git trigger → checkout (from trigger) → ci_shell
Schedule → checkout (from project) → ci_verify
Webhook → checkout (expression repo/ref) → ci_shell

Initial configuration

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

json

{
  "source": {
    "kind": "from_trigger_git"
  }
}

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.