Short answer: You can create or update file in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Create or Update File action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
File Path path | string | Required | File Path. Example: docs/README.md |
Commit Message message | string | Required | Commit Message. Example: Update README |
File Content (base64) content | string | Required | Base64-encoded file content |
Branch branch | string | Optional | Git branch name. |
File SHA (required for updates) sha | string | Optional | Git commit SHA (full 40-char hex, or shortened 7+ chars). |
{"owner": "e.g. octocat","repo": "e.g. hello-world","path": "e.g. docs/README.md","message": "e.g. Update README","content": "{{trigger.content}}"}
{"commit": {"sha": "def456","message": "Update README"},"content": {"sha": "abc123","name": "README.md","path": "docs/README.md"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.