JSON to Google Sheets
Configured with Google Sheets, HTTP Request, Spreadsheet File. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Integration
- Trigger
- Data store
- 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 |
|---|---|---|---|
| HTTP Request | Web / API | HTTP Request | See node parameters |
| Spreadsheet File | Integration | Spreadsheet File | toFile |
| When clicking "Execute Workflow" | Trigger | Manual Trigger | See node parameters |
| Google Sheets | Data store | Google Sheets | append |
| Set | 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
googleSheetsOAuth2Api
Workflow notes
JSON to Google Sheets
JSON to Google Sheets
We map data from the HTTP Request directly in the Google Sheets node, so we don't need a Set node before to transform the incoming data.
JSON to .CSV
JSON to .CSV
We use the Set node to trim down the data that we convert to CSV file format (and flatten it from it's previous object-like data structure). Change settings in Spreadsheet File node to convert to .xls etc.
👋 How to use this template
👋 How to use this template
This template shows how you can load JSON data from an API and load it into an App (Google Sheets) or convert to a file. Here's how to use it:
- Open the
Google Sheetsnode and add a credential (or disabled the node) - Click the
Execute Workflowbutton, then double click the nodes to see their input and output data
To customize this template to you needs:
- Swap
When clicking "Execute Workflow"and theHTTP Requestnode with an App trigger. If we don't have a Native app trigger, just replaceWhen clicking "Execute Workflow"with a Schedule trigger. - Disable or remove parts of the workflow that are not relevant to your usecase.
- Activate the workflow
JSON to Google Sheets
JSON to Google Sheets
Purpose and structure
This folder contains the JSON to Google Sheets workflow. Its executable nodes use googleSheets, httpRequest, manualTrigger, set, spreadsheetFile. 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 "Execute 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/0310_HTTP_Manual_Automation_Webhook.json MIT; preserve source notices.