Before
Someone had to take the file details from an incoming request, open Google Drive, and configure a permission for the intended recipient. The ownership handoff depended on that person completing the permission change for each file.
How it works
- Extract the file identifier and target user from the incoming webhook.
- Create a user permission for the file with ownership transfer enabled.
- Complete the ownership handoff to the specified user in Drive.
Workflow details
- Request intake: The workflow receives a webhook payload and extracts the file identifier and the user who should receive ownership.
- Permission setup: It uses the extracted values to create a user permission for the specified Drive file, with the ownership-transfer option enabled.
- Automated handoff: The workflow applies the new permission directly to the file without requiring someone to open Drive and configure the transfer manually.
- Operational result: The designated user receives the file ownership change initiated by the incoming request, creating a consistent automated process for file handoffs.
What changed
Ownership transfers now begin automatically when the webhook is received. The workflow extracts the required values and applies the permission change directly, removing the manual Drive configuration step.
Work removed
Copying the file identifier and target-user details from the request, opening Drive to locate the file, and manually creating the user permission and ownership transfer.
Expected outcome
One manual permission-creation and ownership-transfer sequence is removed for each successfully processed webhook request.
