The moment it happens
Save files to Drive from any tool
Any tool that can send a file URL to your link gets that file saved into your Drive folder.
- Runs
- The moment it happens
- Apps
- Google Drive
- AI
- Not needed
- Access
- write (drive.file)
Send this to your assistant
Create a ClickRuntime automation: give me a link. When something sends it a file URL and name, download the file, save it to my Inbox folder in Drive and reply with the Drive link.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A marketing team uses a form builder, a scraper, an e-signature tool and a screen recorder, and each of them can produce a file link: a signed PDF, an exported CSV, a recording. The links are temporary, and files stored in each tool's own account are scattered and sometimes deleted after 30 days. Someone has to remember to open each link and drag the file into the right Drive folder, and recordings and signed documents get lost.
ClickRuntime gives you a link that any tool can post to. When a request arrives containing a file URL, it fetches the file, uploads it into your chosen Drive folder with a multipart upload, and returns the Drive link to the caller. A short Slack note tells your team that the file has arrived and where it is.
It is a good fit as a destination for any app that can send a webhook.
What you get out of it
Files saved before links expire
Temporary download URLs often stop working after a few days. Capturing the file the moment the link is sent keeps that signed contract or export from vanishing when the source tool clears its storage.
One place for files from many tools
Instead of searching five accounts for an attachment, everything lands in Drive in a known folder. Anyone with access can find it by search, without having to know which tool created it.
No manual download-and-upload step
The routine of right-click, save, open Drive and upload is easy to forget and slow to do repeatedly. Having the file appear on its own means records are complete without relying on a person's memory.
The sender gets the Drive link back
Because the response includes the link to the saved file, the calling tool can store it, show it to a customer or attach it to a record. The connection becomes useful beyond just filing.
The team knows when it lands
A Slack note on each arrival means people waiting for a signed form or a recording do not have to ask whether it came through. It also shows quickly if a tool has stopped sending files.
How it works
What happens, step by step
When another tool sends ClickRuntime a link to a finished file, it receives the request straight away.
It downloads the file.
The file is saved to your Google Drive folder, using the name you gave or the name from the link.
ClickRuntime replies with a link to the saved file in Drive.
Before it runs live
- Connect Google Drive
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Google Drive steps into one automation
Under the hood
The code that runs this automation
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
from googleapiclient.http import MediaInMemoryUpload
from clickruntime import on_event, credentials, http
INBOX = "inbox-folder-id"
@on_event
def handle(event):
req = event.json or {}
resp = http.get(req["url"], timeout=60)
resp.raise_for_status()
drive = build("drive", "v3", credentials=Credentials(credentials.connection("google", "work")), cache_discovery=False)
saved = drive.files().create(
body={"name": req.get("name") or req["url"].rsplit("/", 1)[-1], "parents": [INBOX]},
media_body=MediaInMemoryUpload(resp.content, resp.headers.get("content-type", "application/octet-stream")),
fields="id,webViewLink",
).execute()
return {"link": saved["webViewLink"]}FAQ
Common questions
What does a tool need to send to the link?
Can the file URL require a login or token?
What happens if a file with the same name already exists?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Create a contract PDF from each form entry
Each form submission becomes a filled-in contract from your template, saved as a PDF in Drive.
See how it worksSet up a shared folder for each new client
Each new client gets a folder with your standard subfolders, shared with them.
See how it worksBack up your data to Drive every night
Each night your data is saved to a dated Drive folder, and backups older than 30 days go to trash.
See how it worksKeep exploring
Set up “Save files to Drive from any tool” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.