Manual file sharing eats up hours every week. Someone exports a report, uploads it to a sharing service, copies the link and pastes it into a chat. Multiply that by every team member and every recurring deliverable and you have a serious productivity problem. The fix is automation. Here are five file-sharing automations that every team should set up.
1. Zapier Triggers for Automatic Uploads
Zapier connects thousands of apps to EasySend without writing a single line of code. The idea is simple: when something happens in one app, Zapier uploads a file to EasySend and sends the share link somewhere useful.
A few practical Zap examples:
- Google Drive to EasySend - When a new file lands in a specific folder, Zapier uploads it to EasySend and posts the share link in a Slack channel
- Form submission to client - When a customer fills out a Typeform, Zapier bundles the attached files and emails the recipient a download link
- CRM deal stage trigger - When a HubSpot deal moves to "Contract Sent," Zapier uploads the PDF contract and sends it to the contact
The key advantage is that non-technical team members can build these workflows in minutes. No API calls, no scripts, no deployment. Just pick a trigger, pick an action and test it. Visit the integrations page for a full list of supported connections.
2. API Scripts for Custom Workflows
When Zapier is too limited or too slow, the EasySend API gives you full control. A single POST request uploads files and returns a JSON response with the share URL, upload token and file metadata.
Here is a Python script that uploads a weekly sales report and emails the link to the team:
import requests
import smtplib
from email.mime.text import MIMEText
# Upload the report
with open('weekly-sales.pdf', 'rb') as f:
resp = requests.post('https://easysend.co/api/v1/upload',
files={'files[]': f})
share_url = 'https://easysend.co' + resp.json()['share_url']
# Email the link
msg = MIMEText(f'Weekly sales report: {share_url}')
msg['Subject'] = 'Weekly Sales Report'
msg['From'] = '[email protected]'
msg['To'] = '[email protected]'
with smtplib.SMTP('smtp.yourcompany.com', 587) as server:
server.starttls()
server.login('user', 'password')
server.send_message(msg)This script runs anywhere Python runs - your laptop, a server or a cloud function. The API requires no authentication for basic uploads, so there is zero setup overhead. Check the API documentation for advanced options like password protection and expiry settings.
3. CLI Cron Jobs for Scheduled Sharing
The EasySend CLI tool is built for automation. Install it once and you can upload files from any shell script. Combine it with cron and you have scheduled file sharing that runs itself.
# Every Monday at 8am, upload the weekly report and log the link
0 8 * * 1 /usr/local/bin/easysend /reports/weekly-$(date +\%Y-\%m-\%d).pdf --json >> /var/log/shared-reports.logCommon cron-based automations include nightly database backups shared with the ops team, weekly analytics exports sent to stakeholders and daily log bundles uploaded for remote debugging. The CLI supports --json output so you can pipe the result into other tools like jq, curl or custom notification scripts.
For a deeper walkthrough, read the CLI automation guide.
4. Slack Bot for Instant Sharing
Your team already lives in Slack. A file-sharing bot lets them upload and share without switching tabs. Type /share quarterly-deck.pdf and the bot uploads the file to EasySend and posts the download link right in the channel.
The bot is a small Node.js app that listens for the slash command, grabs the attached file, sends it to the EasySend API and replies with the link. The entire implementation fits in about 20 lines of code. Your team gets a consistent sharing workflow without ever leaving the conversation.
Beyond the basic upload command, you can extend the bot to handle password-protected shares, set expiry dates or automatically share to specific channels based on file type. A design file goes to #design. A contract goes to #legal. The bot handles the routing.
Full build instructions are in the Slack bot tutorial.
5. Email Notifications on Download
Sharing a file is only half the job. You also need to know when the recipient actually downloads it. EasySend supports email notifications that ping you every time someone accesses your shared link.
Set it up through the web interface by entering your email during upload, or add the --notify flag in the CLI:
easysend contract-v2.pdf --notify [email protected]The notification email includes the download timestamp, the file name and the recipient's general location. This is useful for time-sensitive documents like contracts, proposals and compliance filings where you need confirmation that the other party received the file.
For automated workflows, the API returns a webhook URL that fires a POST request on each download event. Connect it to your project management tool, CRM or internal dashboard for real-time tracking without manual follow-up.
Putting It All Together
These five automations work independently, but they are most powerful when combined. A typical setup might look like this: a cron job generates a report, the API script uploads it, the Slack bot posts the link and email notifications confirm delivery. The entire chain runs without anyone clicking a button.
Start with the automation that solves your biggest pain point. If your team shares files in Slack all day, build the bot first. If you send recurring reports, set up the cron job. If you need accountability, turn on notifications. Each automation saves a few minutes per day and those minutes add up fast.
Explore the API docs and integrations page to get started.
View Integrations