pCloud
StorageManage a pCloud drive from your flows. Agents upload and download files, create and organize folders, generate public share links, and check account storage, with content moving through FlowRunner file storage for use in other steps.
What This Integration Enables
File storage is where automation's outputs either live or get lost, and pCloud is the archive teams pick when they want that storage to be a deliberate choice: region-bound, durable, and plain. FlowRunner treats the drive as the system of record's filing cabinet, and treats filing as work an agent should never skip because it was busy. Content moves through FlowRunner file storage in both directions, so anything uploaded or downloaded is available to every other step in the flow. - Archive invoices, confirmations, and generated reports into structured, dated folders as they are created - Fetch documents for processing in other steps, then store the results back where they belong - Organize the drive programmatically: create, rename, move, and copy files and folders by ID or path - Share files with customers and teammates through public links instead of drifting attachment copies - Check quota and account state before upload-heavy workflows run into a full drive mid-batch
Without FlowRunner
With FlowRunner
Use Case Scenarios
The order archive that files itself
An order completes in [Shopify](/integrations/shopify). The agent builds the archive path for the month, creating it with Create Folder if it is new, and calls Upload File to store the invoice PDF named by order number. List Folder confirms the write landed. When finance needs the month's paper trail, it is one folder, complete and consistently named, instead of a mailbox search.
The contract that travels and comes home
A signature request starts. The agent pulls the master agreement from the drive with Download File, sends it out through [Dropbox Sign](/integrations/dropbox-sign), and when the signed copy returns, Upload File stores it beside the original with a signed suffix. Copy File places a duplicate in the client's own folder, and Rename or Move File retires the draft into /Contracts/Superseded. The drive tells the whole story of the document without a human ever dragging a file.
The delivery link that is not an attachment
A monthly report renders as a PDF. The agent uploads it to the client deliverables folder, calls Get Public Link, and posts the link to [Slack](/integrations/slack) and into the client's row in [Google Sheets](/integrations/google-sheets). The client downloads the canonical file without a pCloud account, and when the report is corrected two days later, the archive holds one truth instead of four attachment generations.
Human-in-Loop Highlight
Delete Folder with Recursive enabled is the most dangerous sentence in this connector: it permanently deletes a folder and everything beneath it, and pCloud's API will do exactly what it is told. Point it at /Archive/2023 and years of invoices are gone; mistype one path segment and it was /Archive/2025. So the retention sweep in FlowRunner never deletes on its own arithmetic. It presents its findings: "4 folders past the 36-month retention window, 2,140 files, 18.2 GB. Full paths and item counts attached. Quota at 91 percent per Get Account Info." The operations owner reads the actual paths and approves the actual list. The same discipline applies in miniature to Get Public Link, because a public link is an exposure decision: anyone holding it can download the file, no account required.
Agent Capabilities
10 actionsFolders
3- List Folder Lists a folder's files and sub-folders by numeric ID (0 is the root) or absolute path, returning each item's name, ids, size, and content type. The browse step before downloads, moves, and every deletion review.
- Create Folder Creates a folder inside a parent specified by ID or path. The step that keeps archives structured instead of aspirational.
- Delete Folder Deletes a folder permanently. Requires the folder to be empty unless Recursive is enabled, which removes the folder and all of its contents. The action this page's human gate exists for.
Files
5- Upload File Uploads a file from a FlowRunner file URL into a pCloud folder, streamed as multipart data, with an optional stored name. The write behind every archiving workflow.
- Download File Downloads a pCloud file into FlowRunner file storage and returns the saved file's URL, ready for any downstream step. The read that lets documents travel through a flow.
- Delete File Permanently deletes a single file by fileid or path. Used in cleanup workflows, under the same review discipline as folder deletion.
- Rename or Move File Renames a file, moves it to a different folder, or both, by fileid or path with a new name and target folder. The organizing instrument for lifecycle moves like draft to signed to superseded.
- Copy File Copies a file into a target folder, optionally under a new name. Used to give clients and teams their own copy without disturbing the canonical one.
Sharing
1- Get Public Link Creates a public download link and short share code for a file. Anyone with the link can download it without a pCloud account, which is exactly why agents log every link they mint.
Account
1- Get Account Info Retrieves the account's email, verification status, total quota, and used space in bytes. The preflight check before upload-heavy runs, and the pressure gauge behind retention reviews.
Frequently Asked Questions
What can FlowRunner do with pCloud?
FlowRunner agents can run List Folder, Upload File, and Download File in pCloud, plus 7 more actions.
Does connecting pCloud to FlowRunner require OAuth?
No. pCloud connects to FlowRunner with an API key, no OAuth flow required.
Can pCloud trigger a FlowRunner workflow automatically?
pCloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with pCloud
$100 in credits. No card required. Connect in minutes.