Short answer: Drop the "Google Sheets → Get Spreadsheet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Spreadsheet ID spreadsheet_id | string | Required | The ID from the spreadsheet URL (between /d/ and /edit) |
Fields fields | string | Optional | Specific fields to return (leave empty for all metadata) |
{"spreadsheet_id": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","fields": "e.g. spreadsheetId,properties.title,sheets.properties"}
{"sheets": [{"properties": {"index": 0,"title": "Sheet1","sheetId": 0,"sheetType": "GRID","gridProperties": {"rowCount": 1000,"columnCount": 26}}},{"properties": {"index": 1,"title": "Sheet2","sheetId": 123,"sheetType": "GRID","gridProperties": {"rowCount": 1000,"columnCount": 26}}}],"properties": {"title": "Sales Tracker","locale": "en_US","defaultFormat": {}},"spreadsheetId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","spreadsheetUrl": "https://docs.google.com/spreadsheets/d/1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms/edit"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.