Special workflows for Google Drive.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
New lead to customer folder
Create a predictable place for approved documents and conversation exports.
Starts when
A Volimox lead becomes qualified or reaches a document-required state.
Result
Every active job has an organized document location tied to the customer record.
Volimox workflow
- 01Volimox creates or finds the configured customer or job folder.
- 02Volimox adds approved intake documents or exports with stable names.
- 03The operator confirms sharing and the folder link is stored on the lead.
Human checkpoint
Folder sharing is explicit and defaults to the least access needed.
Document update to review task
Make a newly added or changed customer file visible to the responsible team.
Starts when
A linked file is created, updated, or moved into the configured review folder.
Result
Document changes produce a controlled review step instead of a silent update.
Volimox workflow
- 01Volimox checks the file path and linked customer or job reference.
- 02Volimox creates a review task with the file link and required decision.
- 03The operator accepts, requests a replacement, or closes the task.
Human checkpoint
Files are not shared with customers until the operator confirms the access policy.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- File created
- File updated
- File moved
Actions
- Create folder
- Upload file
- Move file
- Share file
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Create a controlled lead folder
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runGoogleDriveAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "google-drive",
owner: "me",
})
if (!connection) {
throw new Error("No approved Google Drive connection was found")
}
const result = await zapier.runAction({
app: "google-drive",
action: "create_folder",
connection: connection.id,
input:
{
"parentFolderId": "{{env.GOOGLE_DRIVE_PARENT_ID}}",
"folderName": "{{lead.id}} - {{lead.name}}"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Google OAuth
A reviewable connection, step by step.
- 01Choose a shared drive or folder
- 02Set sharing policy
- 03Review file access scope
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps