Google Sheets

Overview#

Read and append rows in spreadsheets you connect.

Use this block when its responsibility is clear in the graph. Give it a name that describes the work it performs, then test it with representative input before publishing.

Setting it up#

You never see anyone's Google Sheets sign-in, and you do not need your own Google Sheets account to build with this step. People who run the workflow connect their own account and approve exactly what it may do before it starts.

Actions#

• Append a row - Adds a row to the end of the selected sheet. Makes a change. Needs: Row values. Optional: Tab. People running it are asked to allow: _Add rows to the spreadsheet they choose_.
• Read a range - Reads cells from the selected sheet. Only looks things up. Optional: Cells to read. People running it are asked to allow: _Read data from the spreadsheet they choose_.
• Find rows - Finds the rows where a column matches, so a later step can use them. Only looks things up. Needs: Column, Matching. Optional: Cells to read. People running it are asked to allow: _Find rows in the spreadsheet they choose_.

Which spreadsheet it acts on#

• The person running picks a spreadsheet - the default, and the right choice for anything you publish. They choose one of their own spreadsheets before the run starts.
• Always this spreadsheet - fixed to one you name. Use it for a workflow only you will run.
• Any spreadsheet they allow - reaches every spreadsheet their connection covers. They see a clear warning, and the run gets a lower limit on actions.

Filling in the fields#

Every field can be filled three ways: type it (a fixed value), from a step (a value an earlier step produced - pick it from a list, no paths to type), or text + steps (fixed text with values from earlier steps woven in). The panel shows what will be sent, using sample data, and tells you before you publish if a field is missing or points at a step that is no longer connected.

Trying it#

Test runs from the canvas use sample Google Sheets data. Nothing reaches a real account until someone runs the published workflow with their own connection.

Working examples#

These are complete starting points, not decorative diagrams. Every graph is also available in the main template library and is checked by the workflow compiler.

1. Log run results to a sheet#

You will build: One row added to the spreadsheet the runner chose.

A sheet is where most teams already keep records, so nothing new has to be learned. An interrupted append is checked before retrying, so a row is never doubled.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

2. Read a sheet into a summary#

You will build: A plain summary of what the sheet currently holds.

Reading requires no write access, keeping the consent screen minimal. Reads retry safely, so a slow response never fails the run.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

3. Track intake requests#

You will build: Every request captured in one place, timestamped.

Appending is the least invasive way to keep a shared record. The runner picks the spreadsheet, so nothing is written to a sheet they did not choose.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

Ports#

• Input: Input (in): any, optional, multi_object.
• Output: Success (success): object, optional, single.
• Output: Error (error): object, optional, single.

Inspector#

• Action panel: choose what the step does, which account resource it acts on, and where each field's value comes from. See _Setting it up_ above.

Behavior#

• Input requirement: Choose an action. Fields can come from earlier steps or be typed in.
• Execution: Runs through the Edgaze Gateway, which talks to the provider on the runner's behalf.
• Timeout: 30000 ms by default (1000 to 120000 ms).

Cost#

Uses outbound HTTP transport and may contribute to the run's compute cost.

Security#

• The person running the workflow connects their own account and approves exactly what this step may do before the run starts. The workflow never holds their sign-in, and you never see it.
• Actions that make changes are listed separately on the approval screen, and the run is limited to the account resources the person chose.

Retry#

If a step is interrupted mid-change, Edgaze checks with the provider whether the change went through before ever trying again, so nothing is posted or created twice.

Production checklist#

• Test the happy path and one malformed or empty input.
• Keep credentials out of prompts and published graph configuration.
• Set a timeout and retry policy that matches the operation's side effects.
• Name the final result so a runner can tell what success looks like.