An invoice arrives in Gmail. Someone uploads a finished design. A new client needs a folder and a link for sending their documents. Each task is small, but repeating the same steps every week takes time.
The dosya.dev Zapier integration connects your storage to the apps you already use. It can save incoming files, notify a team when work arrives and prepare client folders without requiring you to write code.
Start from our Zapier integration page. It includes the current access link and the operations available in Zapier.
How a file automation works
A Zap begins with a trigger: an event that starts the workflow. It then runs one or more actions, such as uploading a file or posting a message in another app. A search step can find an existing file or folder before the next action runs.
For example, Gmail can trigger a Zap when an attachment arrives, and dosya.dev can upload that attachment into a folder. In the other direction, a new file in a dosya.dev folder can trigger a Slack notification.
Once enabled, the workflow runs in the connected services. You do not need to leave your browser open or keep a desktop app running to execute the Zap.
What dosya.dev gives Zapier
The integration includes three triggers:
| Trigger | When to use it |
|---|---|
| New File | Start a workflow when a new file arrives in a workspace. |
| New File in Folder | Watch a particular folder for new files. |
| Share Link Accessed | Respond when someone opens a share link. |
File triggers work regardless of how the new file reached the workspace. A web upload, desktop upload, rclone sync or SFTP transfer can start the same workflow. Overwriting an existing file does not count as a new file.
There are five actions:
- Upload File: save a file supplied by another app into dosya.dev.
- Upload File From URL: let dosya.dev fetch a file from a public HTTPS URL.
- Create Folder: make a folder in the destination you choose.
- Create Share Link: generate a public file or folder link with optional access code and expiry.
- Create File Request: generate an upload link for someone outside your team.
You can also use Find a File and Find a Folder. Zapier offers the folder search as Find or Create Folder when you want to reuse a matching folder or make it if it is missing.
Three useful workflows to start with
Save Gmail attachments into a folder
Use Gmail’s New Attachment trigger, then dosya.dev’s Upload File action. Choose a workspace and folder, and map the attachment into the file field.
For invoice collection, narrow the Gmail trigger to the messages you want before turning it on. Run a test with a real attachment and check the uploaded file in dosya.dev. This gives you a repeatable filing step whenever a matching message arrives.
Notify Slack when a deliverable arrives
Use New File in Folder for your Deliverables folder, followed by a Slack message action. Include the filename in the message so the team knows what arrived.
If you also want to include a newly generated share link, add Create Share Link between the trigger and the Slack action. Choose an expiry and access code appropriate for the audience. This version needs a Zapier plan that supports the extra step.
Prepare a new client’s folder and upload link
Start with a CRM trigger, such as a HubSpot deal entering the won stage. Use Find or Create Folder to prepare the client’s folder, then Create File Request to generate an upload link for that folder.
The link lets the client submit files without a dosya.dev account. Add a delivery step in your chosen app if you want the Zap to send it to the client automatically. Our file request guide explains how the recipient experience works.
Connect dosya.dev to Zapier
- Open the Zapier integration page. At the time of writing, access is through an invite link while the public directory listing is awaiting approval. Use the page’s access link to add dosya.dev to your Zapier account.
- Create a dosya.dev API key in Profile, then API keys. Choose full scope and leave the folder restriction unset. You can restrict the key to one workspace to limit which workspace the integration can reach.
- Connect dosya.dev in Zapier. Paste the API key when prompted, then choose the workspace and any folder required by your step.
- Build and test one workflow. Confirm the expected file, folder or link appears before enabling the Zap.
The integration can be added on Zapier’s free plan. The apps, number of steps and task volume in your workflow determine which Zapier plan you need. dosya.dev’s storage and API allowances still apply to the account you connect.
Choose a useful event, then automate the next step
Start with one job you already repeat: filing attachments or telling a team that a file is ready. Check a test result, enable the workflow and expand it once the basic steps work as intended.
For link activity, keep the meaning clear. Share Link Accessed tells you that a link was opened; it does not confirm a download or prove the content was read. That distinction helps you write notifications people can trust.
Ready to connect your files to the rest of your workflow? Explore the dosya.dev Zapier integration and build your first automation.
Frequently asked questions
What can I automate with the dosya.dev Zapier integration?
You can react to new files or share link opens, upload files, fetch files from URLs, create folders, create share links and create file requests. The integration also offers file and folder searches so later steps can use material already in your workspace.
How do I connect dosya.dev to Zapier?
Start on the dosya.dev Zapier integration page and use its access link. Create an API key in Profile, then API keys, with full scope and no folder restriction. Paste the key when connecting dosya.dev in Zapier, then choose a workspace and test your first Zap.
Why can I not find dosya.dev in Zapier's app directory?
At the time of writing, the integration is available through an invite link while public directory approval is pending. Open the access link on the dosya.dev Zapier integration page to add it to your Zapier account. That page provides the current access route.
Does Share Link Accessed mean someone downloaded my file?
No. The trigger reports that a share link was opened. It does not prove that someone read the document, watched a video or downloaded the file. Use it for notifications about link activity, with wording that describes an open accurately.
