Drive hygiene report
Starting pointBuilds on the shipped template “Google Drive Workflow” (5 nodes), which you can find in the template library.
Count the files and folders in an area of Drive and report naming problems to its owner.
- List files with the item-type query.
- List folders with the folder query.
- A code node counts both and flags names that break the team’s convention.
- The report goes to the folder owner as output.
Where the approval sits. Nothing here writes to Drive, so no approval is needed. The query is the control.
Scope confirmation before deeper automation
DesignedMake the owner of a Drive area confirm what a later workflow may see.
- List the folders in the area with the list action.
- A human-input step shows the owner the folder names, with approve and reject branches.
- On approval, the confirmed list is passed on as the input that later workflows read their scope from.
- On rejection, the run ends there and the owner’s reason is saved with it.
Where the approval sits. This workflow is the approval. Later workflows read the confirmed scope and do not choose one for themselves.
Onboarding folder check
DesignedCheck that a new starter’s folder has the sections the team expects.
- List the folders in the starter’s area.
- A code node compares the names with the expected list.
- Gaps go to the hiring manager in a human-input step.
- The outcome is passed to the people team as output.
Where the approval sits. Approval confirms the manager has seen the gaps. Creating the missing folders is not in the shipped data, so a person does it.
- Shipped template
- A governed template with its approval step already in it ships in the platform.
- Starting point
- A shipped template runs the same actions. It is an integration test with no approval step, so you add the gate.
- Designed
- Design intent. It uses the actions listed above plus generic nodes, and nothing has been built as a template.