- Support
- Integrations
- Git
Git
Developer Tools integration · 10 node(s) including 1 trigger.
00Overview
Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.
01Connecting Git
Add your credentials as a Flomation environment secret, then pick them in each node. The connection fields are:
| Field | Type | Details | |
|---|---|---|---|
| Authentication | string | Anonymous, SSH Key, HTTP (Username/Password), Token | |
| SSH Private Key | text | Required | |
| Username | secret | Required | |
| Password / Token | string | Required |
Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.
02Add
Git Add
git/add · Action
Stage files for commit in a Git repository
| Field | Type | Details | |
|---|---|---|---|
| File Path | string | . |
Returns: tool_result, success
03Branch
Git Branch
git/branch · Action
Create, list, or switch Git branches
| Field | Type | Details | |
|---|---|---|---|
| Branch Name | string |
Returns: tool_result, success
04Checkout
Git Checkout
git/checkout · Action
Check out a branch or commit in a Git repository
| Field | Type | Details | |
|---|---|---|---|
| Repository Path | string | Required | |
| Branch | string | Required | main |
Returns: tool_result, repository_path
05Clone
Git Clone
git/clone · Action
Clone a Git repository
| Field | Type | Details | |
|---|---|---|---|
| Repository URL | string | Required | |
| Server Host Key — paste the output of `ssh-keyscan <host>`, or a SHA256:... fingerprint. Leave blank to use the runner's known_hosts. | text | ||
| Skip host key verification (INSECURE — an intercepted connection could serve a malicious repository) | boolean |
Returns: tool_result, repository_path, branch, host_key_verification
06Commit
Git Commit
git/commit · Action
Create a Git commit with staged changes
| Field | Type | Details | |
|---|---|---|---|
| Commit Message | text | Required | |
| Author Name | string | Required | |
| Author Email | string | Required |
Returns: tool_result, commit_hash
07Pull
Git Pull
git/pull · Action
Pull latest changes from a remote
| Field | Type | Details | |
|---|---|---|---|
| Server Host Key — paste the output of `ssh-keyscan <host>`, or a SHA256:... fingerprint. Leave blank to use the runner's known_hosts. | text | ||
| Skip host key verification (INSECURE — an intercepted connection could serve a malicious repository) | boolean | ||
| Remote Name | string | origin | |
| Branch | string |
Returns: tool_result, success, host_key_verification
08Push
Git Push
git/push · Action
Push local commits to a remote Git repository
| Field | Type | Details | |
|---|---|---|---|
| Server Host Key — paste the output of `ssh-keyscan <host>`, or a SHA256:... fingerprint. Leave blank to use the runner's known_hosts. | text | ||
| Skip host key verification (INSECURE — an intercepted connection could serve a malicious repository) | boolean | ||
| Remote Name | string | origin |
Returns: tool_result, success, host_key_verification
09Status
Git Status
git/status · Action
Show the working tree status of a Git repository
Returns: tool_result, is_clean, status
10Tag
Git Tag
git/tag · Action
Create or list tags in a Git repository
| Field | Type | Details | |
|---|---|---|---|
| Tag Name | string | ||
| Tag Message | text |
Returns: tool_result, tag_name
11Triggers
Git Poll Trigger
trigger/git_poll · Trigger
Triggers a flow when changes are detected in a Git repository
| Field | Type | Details | |
|---|---|---|---|
| Repository URL | string | Required | git@github.com:org/repo.git |
| Server Host Key — paste the output of `ssh-keyscan <host>`, or a SHA256:... fingerprint. Leave blank to use the Launch service's known_hosts. | text | ||
| Skip host key verification (INSECURE — an intercepted connection could report false commits) | boolean | ||
| Branch Regex | secret | e.g. ^main$ or ^feature/.* | |
| Poll Interval | string | e.g. 60s, 5m |
Returns: branch, commit_hash, commit_message, repository_url
12Notes & Limitations
Behaviours and constraints worth knowing before you build with these nodes.
- Committing captures only the files you first stage with the Add action; edits left unstaged are excluded from the commit even though they remain in the working tree.
- These actions share one working repository and are order-dependent, so a repository must be cloned before Add, Commit, Status, Push or Pull can act on it.
- Pushing to and pulling from a remote require that remote's credentials to be connected; operations against a private remote fail authentication without them.
- Pulling can surface merge conflicts when local and remote history have diverged, and those conflicts must be resolved before the branch can be updated cleanly.
- Checking out a different branch or commit while uncommitted changes exist can be refused or overwrite those changes, so commit them first.