FlowRunner
PricingContact
Theme
Start Free

ShareFile

Storage

Manage documents in ShareFile from agent workflows. Agents browse folders, upload and download files, create and organize items, and generate Send shares to distribute files or Request shares to collect uploads securely.

10 actions API key available
ShareFile website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A new client engagement opens in the CRM with a document checklist attached
Get Root Folder anchors the practice tree, and Create Folder builds the client's engagement folder beneath it
Create Share generates a Request share inviting the client to upload their documents into that folder
The request link goes out to the client with the checklist of what is needed
A daily sweep runs List Children on the engagement folder, matching arrivals against the checklist and chasing what is still missing
Download File pulls each received document into FlowRunner storage for extraction and processing downstream
The engagement manager reviews the assembled deliverable package and approves exactly what goes back to the client
Create Share sends the approved deliverable as a Send share, login required, download notifications on

What This Integration Enables

ShareFile exists because email attachments are how sensitive documents leak, and firms that adopt it are drawing a boundary: client documents cross this line through controlled shares or not at all. The unit of work is the exchange, request, receive, file, deliver, and it is repetitive, deadline-driven, and unforgiving of gaps, which makes it exactly the loop FlowRunner agents should run. The judgment inside the loop, what leaves the firm and who receives it, stays with the people whose names are on the engagement. - Build and maintain client folder structures programmatically, so every engagement starts organized - Collect documents through Request shares and track arrivals against what the engagement actually needs - Move received files into FlowRunner storage for extraction, processing, and forwarding into other systems - Distribute deliverables through Send shares with login requirements and download notifications instead of attachments - Inspect, rename, move, and reorganize items so the tree keeps matching the engagement

Without FlowRunner

Documents travel by attachment Sensitive client files move through inboxes, and the firm's most confidential material has the least controlled channel
Collection by nagging Someone emails the client three times for the missing bank statement, and tracks what arrived in their head
Filing happens at the deadline Everything lands in a downloads folder until the night before, when someone reconstructs the engagement tree

With FlowRunner

Exchanges run on shares Request shares collect, Send shares distribute, and nothing crosses the firm boundary as a loose attachment
Collection is a checklist loop The agent knows what is expected, watches what arrives, and chases the gap automatically
Filed on arrival Every received document lands in the engagement folder it belongs to, the day it arrives

Use Case Scenarios

The order paperwork that ships itself securely

An order completes in [Shopify](/integrations/shopify). The agent creates a per-order folder with Create Folder, uploads the invoice and terms with Upload File, and generates a Send share with Create Share for the customer's copies. The share URL logs to the order record and posts to [Slack](/integrations/slack). When the customer downloads, the notification confirms delivery, which an attachment never does.

The signature loop with a clean chain of custody

A signed agreement lands in the engagement folder. The daily sweep spots it via List Children, confirms its metadata with Get Item, and Download File pulls it into FlowRunner storage. The document routes to [DocuSign](/integrations/docusign) for counter-signature, and when the executed copy returns, Upload File files it beside the original while Rename or Move Item retires the draft to a Superseded subfolder. Anyone auditing the deal later reads the whole history from the folder structure itself.

The document chase that never forgets

Twenty clients owe quarterly documents. The agent builds each client's Request share, sends the links, and then runs the arrivals sweep daily: List Children per folder, matched against each client's checklist held in [Google Sheets](/integrations/google-sheets). Clients with gaps get a specific reminder naming exactly what is missing. The engagement team's Monday report shows collection status per client without anyone opening twenty folders, and the chasing, the part humans do worst, never skips a day.

Human-in-Loop Highlight

Create Share is a boundary crossing. A Send share puts client documents in flight to named recipients, and once the notification lands and the download happens, no revocation undoes the disclosure: the wrong folder shared to the wrong client is a confidentiality incident, not a typo. So FlowRunner agents prepare shares and people release them. The agent assembles the package, lists every item Id and filename it contains, names the recipients, and states the settings: login required, notifications on. The engagement manager reads that manifest and approves the send. The same one-way logic governs Delete Item, which permanently removes a file, or a folder with everything in it, so cleanup batches get the identical treatment: verified with Get Item, listed in full, approved by a person, then executed.

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

10 actions

Items

7
  • Get Root Folder Retrieves the authenticated user's home folder with its Id and metadata. The anchor from which folder trees are built and browsed.
  • Get Item Retrieves a single file or folder's metadata by Id: name, size, parent, creation date. The verification step before renames, moves, downloads, and every deletion.
  • Get Item By ID Resolves an item by Id from the account root, without needing its containing folder context. The lookup for items whose Ids arrive from logs or other systems.
  • List Children Lists a folder's direct children with each item's Id, name, size, and folder flag. The sweep read behind arrival tracking and folder audits.
  • Create Folder Creates a subfolder inside a parent, with optional description and an Overwrite option to reuse an existing folder of the same name. The step that keeps every engagement starting from the same structure.
  • Rename or Move Item Renames an item, updates its description, or moves it to a new parent folder, changing only the fields supplied. The lifecycle instrument for draft, signed, and superseded states.
  • Delete Item Permanently deletes a file or folder by Id, including all of a folder's contents. Cannot be undone, which is why it runs only on human-approved lists.

Files

2
  • Upload File Uploads a file from a FlowRunner file URL into a folder using ShareFile's two-step upload flow. The write behind archiving and deliverable staging.
  • Download File Downloads a file's contents into FlowRunner storage and returns the saved file's URL, ready for any downstream step. The read that lets client documents enter processing pipelines.

Sharing

1
  • Create Share Creates a Send share to distribute files or a Request share to collect uploads, with optional title, required login, and download notifications. The boundary-crossing action this page's human gate governs.

Frequently Asked Questions

What can FlowRunner do with ShareFile?

FlowRunner agents can run Get Root Folder, Get Item, and Get Item By ID in ShareFile, plus 7 more actions.

Does connecting ShareFile to FlowRunner require OAuth?

No. ShareFile connects to FlowRunner with an API key, no OAuth flow required.

Can ShareFile trigger a FlowRunner workflow automatically?

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

Start building with ShareFile

$100 in credits. No card required. Connect in minutes.