Spreadsheet Append
Append a row to a Google Sheet or a local CSV file.
What it does
Takes a row from memory (as an array or an object) and appends it to a spreadsheet. For Google Sheets, the integration uses an API token you provide. For local CSV files, the integration writes to disk directly.
This is the easiest way to keep a running log of automation results without setting up a database.
What you configure
| Field | What it controls | Required | Notes |
|---|---|---|---|
| Target | The spreadsheet ID (Google Sheets) or file path (CSV). | required | Use the Google Sheet's ID from its URL, or an absolute path on the server. |
| Auth token | Google Sheets API token. | required for Google Sheets | Stored as a secured value. Not needed for local CSV. |
| Data (memory input) | The row to append. | required | An object becomes a row with column names as keys; an array becomes a row in column order. |
📷 SCREENSHOT: The Spreadsheet Append step with the target field showing a Google Sheets ID and a data memory selector.
Example scenario
Lead tracking. A webhook trigger receives an incoming sign-up. An LLM Prompt enriches the data (industry, likely use case). A Spreadsheet Append step adds one row per signup to a Google Sheet that the sales team already uses.
Recommendations
- ✅ Keep the column order stable. Adding a column in the middle later requires care; appending at the end is safe.
- ✅ For Google Sheets, use a service-account API token rather than a personal one. Personal tokens disappear when the person leaves.
- ✅ Use objects rather than arrays as input. Objects survive column reordering; arrays do not.
- ⚠️ Google Sheets has an API quota. Many appends per minute can hit it.
- ❌ Do not use this integration as a primary data store. For real volume, write to a database.
What to do next
- For long-term structured storage: Database Query (to write rows) or a Database Listener (to consume rows).
- For arbitrary file output: File Writer.