Google Drive

Overview#

Save and read text files created by Edgaze.

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 Drive sign-in, and you do not need your own Google Drive 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#

• Save a text file - Saves text as a file in the person's Drive, visible as created by Edgaze. Makes a change. Needs: File name, File contents. People running it are asked to allow: _Save files to your Drive_.
• List Edgaze files - Lists files Edgaze created in the person's Drive. Only looks things up. Optional: Maximum files. People running it are asked to allow: _See the Drive files Edgaze created_.
• Read a text file - Reads the contents of a saved text file. Only looks things up. People running it are asked to allow: _Read the file they choose in your Drive_.

Which file it acts on#

• The person running picks a file - the default, and the right choice for anything you publish. They choose one of their own files before the run starts.
• Always this file - fixed to one you name. Use it for a workflow only you will run.
• Any file they allow - reaches every file 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 Drive 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. Save a report as a file#

You will build: The report lands in Drive as a plain-text file.

Edgaze can only touch files it created or the person opened with it. Their Drive stays their own. An interrupted save is checked by file name before retrying.

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

2. List Edgaze-made files#

You will build: A list of what the workflow has actually saved.

drive.file scopes visibility to Edgaze-created files, so listing is safe by construction. Reads retry safely, so a transient Drive outage never fails the run.

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

3. Read back a saved file#

You will build: The workflow answers from the file's saved text.

Only files the run picks are ever read. Reads retry safely; nothing is written.

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.