Short answer: Drop the "Google Sheets → Add Sheet Tab" 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) |
Sheet Name title | string | Required | Name for the new sheet tab |
Row Count rowCount | string | Optional | Number of rows (default: 1000) |
Column Count columnCount | string | Optional | Number of columns (default: 26) |
{"spreadsheet_id": "e.g. 1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms","title": "e.g. January Data","rowCount": "1000","columnCount": "26"}
{"replies": [{"addSheet": {"properties": {"index": 2,"title": "January Data","sheetId": 12345,"sheetType": "GRID","gridProperties": {"rowCount": 1000,"columnCount": 26}}}}]}
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.