FlowRunner
PricingContact
Theme
Start Free

Folderit

Storage

Folderit is a cloud document management system with folders, versions, metadata, tags, sharing, and a full audit trail. Agents file incoming documents, build client folder structures, search by content, tag and describe files, and read who did what.

36 actions OAuth available
Folderit website Platform Documentation Capability data verified 2026-08-13
A countersigned vendor agreement lands in the shared finance mailbox
Agent reads the vendor name, effective date, and renewal term off the document
Upload File places it in that vendor's folder under the right account
Set File Metadata writes the effective date and renewal term into the account's own metadata fields
Add File Tags applies the tags the vendor's category already uses, rather than inventing new ones
Get File Audit Trail confirms the upload registered against the expected file and user
Before the agreement is shared out to the vendor contact by email, a person confirms who receives it

What This Integration Enables

Folderit is for teams that need provable document history without buying an enterprise content management program to get it. The product is the audit trail, the metadata fields, and the recycle bin, and the connector reflects that: for almost every destructive operation there is a matching recovery. Delete Folder has Restore Folder. Delete File has Restore File. Lock File has Unlock File. Add File Tags has Remove File Tag. A finance team that files three hundred documents a month can let an agent do it precisely because a wrong move is a reversible move.

That inverts the usual risk profile for a storage connector, and it changes where the human-in-the-loop gate belongs. Agents file incoming documents into the right client or vendor folder, build a folder structure from a record instead of by hand, set the metadata and tags that make a document retrievable, search the store by what is inside a document, and answer audit questions from the trail rather than from recollection. The single operation with no recovery behind it is the one that reaches a person outside the account, and that is the one the agent hands over.

Without FlowRunner

Filed by hand, described by nobody Documents arrive with a filename and no metadata, so finding one later means opening several
Search that only reads names "The lease with the escalation clause" gets found from memory rather than from a query
History reconstructed after the fact Answering who opened a document means asking people what they remember

With FlowRunner

Filed and described in one pass Upload File, Set File Metadata, and Add File Tags run together, so a document is findable the moment it lands
Search that reads contents Search Files looks inside documents, so a flow can find the right one and act on it
History read from the trail Get File Audit Trail answers who opened, changed, or shared a document, with the times attached

Use Case Scenarios

  • Intake that describes itself

    Documents arrive as attachments in Gmail. The agent reads the counterparty, document type, and key dates off the content, then calls Search Folders to find the counterparty's existing folder, or List Sections and Create Folder to build it when the counterparty is new. Upload File places the document. List Metadata Fields tells the agent which fields this account actually defines, so Set File Metadata writes into the schema the firm chose rather than a generic one, and List Tags is read before Add File Tags so the tagging stays consistent with what already exists. A month later, Search Files finds the document by its contents and its metadata, which is the only reason any of this filing work matters.

  • The renewal calendar that builds itself

    On a schedule, the agent runs Search Files against the contract sections and calls Get File Metadata on each result to read the effective date and renewal term. Agreements renewing inside the notice window get appended to a register in Google Sheets and posted as a grouped summary to the finance channel in Slack, each line carrying the document name and its folder. Nothing about the documents changes. The agent is reading a filing system as though it were a database, which is exactly what the metadata fields were put there for.

  • Answering the auditor without opening the app

    An auditor asks who had access to a set of documents during a period. The agent calls List File Shares for each document to read current sharing, Get File Audit Trail for the per-document history of opens, changes, and shares, and Get Account Audit Trail for the wider activity around the same window. It assembles one dated summary and files it back into the audit folder with its own metadata set, so next year's request starts from a document rather than from scratch. Where the trail shows access that looks wrong, the agent reports it rather than revoking it, because a share withdrawn mid-audit is a fact somebody will have to explain.

Human-in-Loop Highlight

Nearly everything in Folderit can be undone, which is what makes the exception so sharp. Share File by email address does not just grant access, it sends that person an invitation from Folderit. Delete Share withdraws the access afterwards, but it does not unsend the email, and it does not unread the document. In a records system holding client agreements and payroll files, an invitation sent to the wrong address is the one action with no restore behind it. So when a flow reaches an outbound share, the agent stops and asks in the finance channel: "The Halberd Group master agreement is ready to send. The vendor contact on the record is [email protected], which does not match the domain on the signature block, halberdgroup.example. Share to the address on the record, share to a different address, or hold?" It has already gathered the document, the existing shares from List File Shares, and the mismatch. Sharing with an existing user or group inside the account carries none of this weight, and the agent does that on its own all day. The invitation that leaves the building waits for a person.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

36 actions

Accounts

3
  • List Accounts Lists the accounts this connection can reach. Almost everything else needs one of these.
  • Get Account Reads one account.
  • Get Current User Reads the user the connection signs in as. Useful for checking a connection works before a flow depends on it.

Folders

8
  • List Sections Lists the top-level folders of an account. Folderit calls these sections.
  • Get Folder Reads one folder.
  • List Subfolders Lists the folders directly inside a folder.
  • List Files In Folder Lists the files directly inside a folder.
  • Create Folder Creates a folder. Leave the parent empty to create a top-level section instead.
  • Rename Folder Changes a folder's name.
  • Delete Folder Moves a folder to the recycle bin along with everything in it. Restore Folder brings it back; purging does not.
  • Restore Folder Takes a folder back out of the recycle bin.

Files

10
  • Get File Reads a file's details, without downloading it.
  • Upload File Uploads a file from a URL into a folder. Folderit uploads in three steps and this does all of them.
  • Download File Downloads a file and stores it in file storage.
  • List File Versions Lists the versions Folderit keeps of a file.
  • Rename File Changes a file's name or the note held against it.
  • Delete File Moves a file to the recycle bin. Restore File brings it back; purging does not.
  • Restore File Takes a file back out of the recycle bin.
  • Lock File Locks a file so nobody else edits it while you are working on it. Used when a flow is mid-way through a multi-step revision.
  • Unlock File Releases a lock on a file.
  • List Recycled Files Lists the files sitting in the recycle bin, which is where a cleanup sweep checks its own work.

Search

2
  • Search Files Searches the files in an account by name, contents, metadata, or tag. The operation that makes the filing work pay off.
  • Search Folders Searches the folders in an account by name. Used to resolve a client or vendor folder before filing.

Tags

5
  • List Tags Lists the tags defined on an account. Read before tagging so an agent reuses the firm's vocabulary.
  • Create Tag Creates a tag, optionally underneath another one.
  • List File Tags Lists the tags on a file.
  • Add File Tags Puts one or more existing tags on a file.
  • Remove File Tag Takes one tag off a file. The tag itself is left alone.

Metadata

3
  • List Metadata Fields Lists the metadata fields defined on an account, so a flow writes into the schema the firm actually chose.
  • Get File Metadata Reads the metadata values held against a file.
  • Set File Metadata Puts a value into one of the account's metadata fields on a file.

Sharing

3
  • List File Shares Lists who a file is shared with.
  • Share File Shares a file with somebody. Sharing by email invites that person and Folderit emails them, which is why this page's human gate sits here.
  • Delete Share Withdraws a share, so whoever it was shared with loses access from that point on.

Audit

2
  • Get File Audit Trail Reads what has happened to a file: who opened it, changed it, or shared it.
  • Get Account Audit Trail Reads recent activity across the whole account.

Frequently Asked Questions

What can FlowRunner do with Folderit?

FlowRunner agents can run List Accounts, Get Account, and Get Current User in Folderit, plus 33 more actions.

Does connecting Folderit to FlowRunner require OAuth?

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

Can Folderit trigger a FlowRunner workflow automatically?

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

Start building with Folderit

Free plan, no card required. Connect in minutes.