Put.io

Put.io is cloud storage that downloads for you from an HTTP URL or a magnet link. Agents start transfers, watch RSS feeds and fetch matching items, unpack archives in place, bundle files into ZIPs, and share or pull the results down.

43 actions OAuth available

Put.io website Platform Documentation Capability data verified 2026-08-13

A client posts the delivery URL for a large master file

Add Transfer hands the URL to Put.io, so the bytes never cross the flow at all

Get Transfer is polled for progress and for an error message rather than for silence

Extract Files unpacks the delivered archive in place, without downloading it first

Convert To MP4 produces a review copy from the master

Create Zip bundles the review set and the agent posts the resulting link to the project channel

Before a standing feed rule is created to fetch a source automatically, a person approves the rule

What This Integration Enables

Put.io is not competing to be your document store. It is storage with a fetcher attached, and that one property is the reason to use it inside a workflow. Hand it an HTTP URL or a magnet link and it does the downloading on its own network, so a fifty gigabyte master file never travels through your flow, your laptop, or your egress bill. What arrives can then be unpacked, converted, or bundled where it already sits.

Everything else in the connector follows from that. Transfers are first-class objects with progress, speed, and error messages, so a workflow can tell a stalled fetch from a failed one. Archives extract server side and videos convert server side, so the heavy work happens next to the bytes. Create Zip turns a selection into a single link somebody can be given. And RSS feeds turn acquisition into a standing rule rather than a request. That last capability is powerful enough to need a boundary, which is where FlowRunner's human-in-the-loop model comes in: an agent can build an unattended fetch rule perfectly well, and it still should not be the thing that decides one exists.

Without FlowRunner

Large files pulled through your own pipe A multi-gigabyte delivery is downloaded to a laptop and uploaded somewhere else, twice over the same connection

Failures noticed late A transfer that errored looks exactly like one that has not started until somebody goes and checks

Repackaging done by hand Sending a subset means downloading it, zipping it locally, and finding somewhere to host the result

With FlowRunner

Storage does the fetching Add Transfer takes the URL or magnet link, and the flow only ever handles the finished result

Failures surfaced with a reason Get Transfer carries progress, speed, and the error message, so a retry is a decision rather than a guess

Repackaging done in a call Create Zip builds the bundle server side and Get Zip hands back the link

Use Case Scenarios

The delivery your network never touches

A client drops a link to a multi-gigabyte master in the project thread. The agent calls Add Transfer with the URL and Put.io begins fetching immediately. Rather than holding a connection open, the flow polls Get Transfer for progress and for the error field, which means a transfer that fails reports why instead of just never finishing. When it completes, Extract Files unpacks the delivered archive in place, List Files reads what came out, and only the specific assets the project needs are moved on to Amazon S3 / Cloud Storage or Google Drive. The agent posts a summary to Slack with the file list and the elapsed transfer time from the transfer record.
A review copy without a render farm

A finished video sits in the account at full master quality, which is not what a reviewer wants to open on a phone. The agent calls Convert To MP4 and polls Get MP4 Status until the conversion reports done, then calls List Subtitles to see which tracks Put.io found and Download Subtitle for the one the reviewer needs. Get Download URL returns a direct link, so the review copy can be handed on without the file passing through the flow at all. The master stays where it is, untouched and unconverted.
Keeping the account honest about space

The account has a finite amount of room, and unattended fetching fills it. On a schedule, the agent calls Get Account Info to read how much space is used and left, List Transfers to find anything sitting in an error state, and Retry Transfer once on the ones that look transient. Clean Transfers clears the finished entries off the list, and Remove Transfers takes out the ones already filed elsewhere, without touching the files they produced. Where the free space crosses a threshold, the agent lists the largest folders with List Files and reports them as one of the automation exceptions a person clears, rather than deleting anything to make room.

Human-in-Loop Highlight

Create Feed is a standing instruction, and that is a different kind of thing from an action. A feed watches a source and transfers every item whose title matches its filters, into an account with finite space, without anybody looking at the individual items first. Pause Feed and Delete Feed stop future transfers, but what a feed has already brought in stays in the account, which means the rule's output outlives the rule. The account is answerable for what lands in it, and the agent has no way to judge whether a given source should be pulling into it unattended. So the agent does the setup and stops at the switch: "Create a feed on the client's delivery RSS at feeds.northgate.example/masters, filtered to titles containing NG-2026 and excluding PROXY, delivering to /Clients/Northgate/Inbound. That is an open-ended instruction: everything matching will transfer without review, and the account is currently at 62 percent of its space. Create it, or should I fetch this week's items with Add Transfer instead?" One-off fetches the agent runs by itself all day. A rule that fetches forever gets a name on it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

43 actions

Files and Folders

List Files Lists the files and folders inside a folder. Listing is not recursive.
Continue Listing Files Fetches the next page of a file listing, using the cursor the previous page returned.
Search Files Searches your files and your friends' files by keyword.
Continue Searching Files Fetches the next page of search results, using the cursor the previous page returned.
Get File Reads one file or folder, optionally with its codec and media details.
Get Download URL Reads a direct download URL for a file, without downloading it. Used to hand a file on without routing the bytes through the flow.
Download File Downloads a file from Put.io and stores it in file storage.
Upload File Uploads a file from a URL into a Put.io folder.
Create Folder Creates a folder inside another folder.
Rename File Renames a file or folder in place.
Move Files Moves one or more files into another folder.
Delete Files Deletes one or more files or folders. Deleting a folder takes everything in it, so cleanup flows list before they delete.

Media Processing

Extract Files Unpacks ZIP and RAR archives already in Put.io. The work happens in the background, next to the bytes.
List Extractions Lists the archive extractions currently running.
Convert To MP4 Asks Put.io to make an MP4 of a video file. The conversion runs in the background.
Get MP4 Status Reads how an MP4 conversion is getting on.
List Subtitles Lists the subtitle tracks available for a video, including ones Put.io found itself.
Download Subtitle Downloads one subtitle track and stores it in file storage.

Transfers

List Transfers Lists every transfer on the account, running and finished. The sweep that finds anything stuck.
Get Transfer Reads one transfer with its progress, speed, and any error message, which is what turns a stall into a diagnosable event.
Add Transfer Starts a transfer from an HTTP URL or a magnet link. Put.io fetches it into your storage.
Cancel Transfers Cancels transfers that are still running.
Retry Transfer Starts a failed transfer again. Worth doing once automatically, and reporting after that.
Remove Transfers Removes transfers from the list. The files they downloaded stay where they are.
Clean Transfers Clears finished transfers off the list.

ZIP Bundles

Create Zip Asks Put.io to build a ZIP of the files you name. Getting the link is a second step.
List Zips Lists the ZIP jobs currently running.
Get Zip Reads a ZIP job. Once it is finished the response carries the download URL.

Sharing

Share Files Shares files with named friends, or with everyone on your friends list.
List Shared Files Lists the files you have shared with other people. The sweep that finds shares nobody remembers.
List File Shares Lists who a particular file is shared with.
Unshare File Stops sharing a file with the people you name.

RSS Feeds

List Feeds Lists the RSS feeds Put.io is watching for you.
Get Feed Reads one RSS feed with its filters and its destination folder.
Create Feed Watches an RSS feed and transfers matching items automatically. A standing instruction, and where this page's human gate sits.
Update Feed Changes an RSS feed's destination, filters, or paused state.
Pause Feed Stops an RSS feed transferring anything new.
Resume Feed Starts a paused RSS feed again.
Delete Feed Deletes an RSS feed. Files it already transferred stay where they are.

Account and Activity

Get Account Info Reads the account: username, plan, and how much space is used and left. The number that decides whether unattended fetching is still safe.
Get Account Settings Reads the account's own preferences, such as its default download folder.
List Events Reads the account's activity feed: transfers completed, files shared, and so on.
Clear Events Clears the activity feed. It does not touch files or transfers.

Frequently Asked Questions

What can FlowRunner do with Put.io?

FlowRunner agents can run List Files, Continue Listing Files, and Search Files in Put.io, plus 40 more actions.

Does connecting Put.io to FlowRunner require OAuth?

Yes. Put.io connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Put.io trigger a FlowRunner workflow automatically?

Put.io doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Put.io

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us