Cloud Conversion Workflows
Convert files between Drive, Dropbox, OneDrive, S3, and more on a schedule. Set up once, let cron do the rest โ no scripts, no servers, no babysitting.
How a workflow run looks
Source bucket โ ConvertIntoMP4 โ destination bucket โ fired on a cron schedule you control.
Sources
- Google Drive
- Dropbox
- OneDrive
Schedule
0 2 * * *
Cron-driven, runs in UTC. Minimum interval is 5 minutes.
Destinations
- Amazon S3
- Azure Blob
- Google Cloud Storage
- SFTP
- Google Drive
What teams actually do with scheduled workflows
Four real patterns we see daily. Each is a single workflow โ no code, no servers to maintain.
Nightly video transcoding pipeline
Drop raw MOV recordings into a Dropbox folder during the day. At 2 AM, ConvertIntoMP4 transcodes them to web-ready MP4 and delivers them to your S3 origin for the CDN.
Weekly invoice batch (PDF โ OCR'd PDF)
Every Monday morning, scoop up the week's scanned invoices from a Google Drive folder, run them through OCR, and push the searchable PDFs to your SFTP archive for accounting.
Real-time DOCX โ PDF for legal
Watch a OneDrive folder every 15 minutes. New DOCX contracts get rendered to print-ready PDF and dropped into an Azure Blob container for e-signature workflows.
Cross-cloud migration
Moving from Drive to GCS, or Dropbox to S3? Set up a one-shot workflow that walks the source bucket, converts where needed (HEIC โ JPG, MOV โ MP4), and writes to the destination.
Sample cron expressions
Copy any of these into your workflow's schedule field. Aliases (@daily, @hourly, @weekly) also work.
| Cron expression | Plain English |
|---|---|
| 0 2 * * * | Every day at 2:00 AM (UTC) |
| */15 * * * * | Every 15 minutes |
| 0 9 * * MON | Every Monday at 9:00 AM (UTC) |
| 0 0 1 * * | First day of every month at midnight |
| 0 */6 * * * | Every 6 hours (00:00, 06:00, 12:00, 18:00) |
| 0 9 * * 1-5 | Weekdays at 9:00 AM (UTC) |
How it works
Four steps from zero to a workflow running on its own.
- Step 1
Connect your cloud source
OAuth into Google Drive, Dropbox, or OneDrive from your dashboard. ConvertIntoMP4 stores a short-lived access token in Redis and refreshes it automatically โ your password is never seen.
- Step 2
Choose source and target format
Pick the file type you'll be feeding in (MP4, DOCX, PDF, MOV โ 255 formats supported) and the format you want out. Per-format options like bitrate, resolution, and PDF compression are available.
- Step 3
Set the cron schedule
Pick from a preset (nightly, hourly, weekly) or write your own 5-field cron expression. Workflows run on UTC. Future runs are shown in plain English in the dashboard.
- Step 4
Configure destination delivery
Send converted output back to the same cloud, a different cloud (S3, Azure Blob, Google Cloud Storage, SFTP), or even your own Google Drive. Webhook on completion is optional.
Ready to automate?
Workflows are free to create โ you only pay for the conversions they run. Sign in or create a free account to deep-link straight to the dashboard.
Donโt want to write JSON? Build it visually โ Job Builder
Frequently asked questions
Everything you need to know before you set up your first workflow.
What happens if a conversion fails mid-workflow?
Each file conversion in a workflow run is independent. If one file fails (corrupt input, unsupported variant), it's logged with a structured error and the run continues with the next file. The full run report is delivered via webhook on completion, and the dashboard shows a failure count alongside the success count. Failed jobs are retried up to 3 times with exponential backoff before being marked permanently failed.
Which cloud sources and destinations are supported?
Sources: Google Drive, Dropbox, OneDrive (Microsoft 365 + personal). Destinations: Amazon S3, Azure Blob Storage, Google Cloud Storage, SFTP, and Google Drive. Every source uses OAuth โ we never ask for your password. Every destination uses short-lived credentials stored encrypted at rest. You can mix and match (e.g. pull from Dropbox, push to S3).
How many files can a single workflow process per run?
The cap is per-plan. Free workflows process up to 25 files per scheduled run, Pro processes up to 500, and Business processes up to 2,000. Enterprise plans are uncapped. Large folders are paginated automatically โ the workflow walks the source folder using the cloud provider's native cursor and queues each file as a separate conversion job, so a 1,500-file Drive folder is fully supported on Pro.
How am I notified about errors or completed runs?
Three channels: (1) webhook delivery to your endpoint with HMAC signing, the same envelope used for one-off conversions, but with a `workflow_run.completed` event type; (2) email summary on every run (configurable to error-only); (3) the workflow dashboard at /account/workflows shows the last 30 runs with file-level success/failure counts and links to each conversion's job log.
Are there limits on cron expressions or how often a workflow can run?
Yes โ minimum interval is 5 minutes. Cron expressions must be standard 5-field POSIX format (minute, hour, day-of-month, month, day-of-week). Aliases like @hourly, @daily, @weekly, and @monthly are accepted. Sub-minute schedules and 6-field (seconds) cron are not supported. All workflows run in UTC; the dashboard converts to your timezone for display only.
How much do Cloud Workflows cost?
Workflows themselves are free โ you only pay for the conversions they run. Pricing follows the standard ConvertIntoMP4 plan: Free includes 50 conversions/day, Pro ($9.99/mo) includes 2,000/day, Business ($24.99/mo) includes 20,000/day, and the API plan is pay-per-credit. There's no per-workflow surcharge and no markup on the cloud storage costs (you provide your own S3/Azure/GCS credentials).