Sound familiar?
What teams that manage work in Asana and keep files in Google Drive tell us before a project starts.
- Project folders are created by hand.
- Folder names don't match projects.
- Files are attached in tasks and lost.
- Sharing is set up again for each client.
- Finished work is scattered.
What we build
Each one is a working piece you can open and check when it's done.
Automation
- Folders from a template
- Sharing
- Links
- Filing
- Google Drive updated
- Run logged
- Any failure sent to you
Folders from a template
A Drive folder structure created when a project starts.
Google Sheets and Apps Script automationLogging and alerts
Every run is logged, and anything that cannot sync is sent to you with the reason.
Python scripts and utilitiesThe two tools: Asana, Google Drive.
Also connected on request: Asana, Google Drive.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Marketing agency
Example: an agency wants a client folder with briefs, drafts and finals created for each new Asana project.
Asana API, Google Drive APIExample project
Architects
Example: a studio wants drawings moved to an issued folder when the Asana task is marked done.
Asana webhooks, Google Drive APIQuestions people ask first
Doesn't Asana attach Drive files already?
Yes, one at a time. This sets up folders, sharing and filing for you.
Can it work with shared drives?
Yes.
Can folder names follow our convention?
Yes, names come from the project fields you choose.
Want this as a ready-made pack?
We are turning the most requested integrations into ready-made n8n workflows you import and run in your own accounts. Tell us you want this one and we will email you when it is ready.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com