Point a compatible camera at one address. Use FTP, explicit FTPS, or SFTP, depending on what the camera supports.
Scoped credentialWe uploaded and verified the same JPEG over all three protocols.Send each file where the job needs it.
Connect Dropbox, Google Drive, Frame.io, or your own storage once, then choose the exact folder for each flow. Your camera keeps one Camera to Anywhere login, so none of those services ever receive its password.
Working now
We sent real files through each route below and verified the copy at the other end.
Pick a Dropbox folder for a flow, then each camera file goes there as it arrives.
OAuth 2.0A live JPEG arrived with a Dropbox receipt and the correct delivery charge. Dropbox still needs to approve the production app.Run the relay on a machine that can see your NAS. It pulls finished files over HTTPS, so you do not open an inbound port.
Paired outbound agentA live SFTP upload reached the paired NAS folder and matched the original file.Pick a Google Drive folder for the flow. Large files resume from the last completed part if a connection drops.
OAuth 2.0A JPEG and a large video reached Drive with receipts and the correct delivery charge.Choose the Frame.io account, workspace, project, and folder that should receive the flow.
Adobe IMS OAuth 2.0A live JPEG reached the selected project with a Frame.io receipt and the correct delivery charge. Adobe still needs to approve the production app.Built, waiting on access
The code is finished. We still need a provider credential, production approval, or a real account to run the last upload.
Send large files in resumable parts to a bucket you control.
Scoped cloud credentialCloudflare R2 passed with a real file. Amazon S3 still needs a customer AWS account for the final test.Pick a OneDrive folder and send each finished camera file through Microsoft Graph.
Microsoft OAuth 2.0Sign-in and the upload code pass in tests. We still need a real OneDrive account for the folder and delivery run.Send small files directly and split large files into resumable parts, then check the SHA-1 that Box returns.
OAuth 2.0The upload and token-refresh code pass in tests. We still need a real Box account for the folder and delivery run.Send files through PhotoShelter’s Incoming FTP account with explicit TLS.
Incoming FTPS credentialWe still need a live Incoming FTP account, and PhotoShelter needs to confirm whether its newer API can replace that route.Choose an album you own, then send photos and video into it as the camera uploads.
OAuth 1.0aWe still need SmugMug API credentials, a live upload, and a paid-download test.Choose an active gallery with a price sheet, then send JPEGs through ShootProof’s upload flow.
OAuth 2.0We still need a ShootProof client ID, a live upload, and a purchase test.Send the finished copy into a Slack channel the Camera to Anywhere bot has joined, with its final filename intact.
Slack OAuth 2.0 bot grantSign-in, channel selection, receipts, retry, and billing pass in tests. We still need one live channel delivery.Next
We have scoped these routes, but you cannot add them to a flow yet.
Send files to a server, storage appliance, or hosted folder using its existing WebDAV or SFTP login.
Protocol credentialWe have designed this route, but the outbound upload code does not exist yet.