Push Multiple Files to Github Repo via Github REST API
Configured with HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Get latest commit SHA | Web / API | HTTP Request | See node parameters |
| Get base tree SHA | Web / API | HTTP Request | See node parameters |
| Create new tree | Web / API | HTTP Request | POST |
| Create commit | Web / API | HTTP Request | POST |
| Update branch | Web / API | HTTP Request | PATCH |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Set Github Info | Transform | Edit Fields | See node parameters |
| File 1 | Transform | Edit Fields | See node parameters |
| File 2 | Transform | Edit Fields | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Push Multiple Files to GitHub Repo
Push Multiple Files to GitHub Repo
A streamlined workflow for uploading multiple files to a GitHub repository via the GitHub REST API. This solution addresses a significant limitation of the native GitHub n8n node, which supports only single-file uploads.
This approach enables batch file operations, making it particularly valuable for automation scenarios that require simultaneous uploads of multiple files to your GitHub repositories.
Setup Instructions:
- Create a new GitHub Personal Access Token here. In the "Repository access" section, select your repository and grant "Read and write" permissions under the "Contents" category.
- Configure your GitHub information in the "Set GitHub Info" node.
- Update the "Create New Tree" node with your filenames and content. You can add as many tree entries (files) as needed.
Push Multiple Files to Github Repo via Github REST API
Push Multiple Files to Github Repo via Github REST API
Purpose and structure
This folder contains the Push Multiple Files to Github Repo via Github REST API workflow. Its executable nodes use httpRequest, manualTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1640_HTTP_Stickynote_Automation_Webhook.json MIT; preserve source notices.