Revver
StorageRevver, formerly eFileCabinet, is enterprise document management organized as a tree of folders and files. Agents file documents into the right node, share them through links and collections, issue document requests, and pull signed contracts out for the next step.
What This Integration Enables
Revver, formerly eFileCabinet, is a records system that happens to hold files. Everything in it is a node in a tree, and the operations that matter are the ones that decide a document's standing after it is filed: which access link lets somebody outside reach it, which collection it belongs to for an audit, which document request is still unanswered, and which signature transaction is still open. A team picks Revver when the folder a document lives in is part of the record, not a convenience.
FlowRunner agents work that tree directly. They read a client name off an incoming document and upload it to the right node, build a whole client folder structure from a record, search the store by what is inside a document rather than by filename, and pull executed contracts out the moment the signing provider reports them done. What the connectors do not do is decide anything that reaches a counterparty. That boundary is deliberate, and it is where FlowRunner's human-in-the-loop model does its work.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
The executed contract stops being a to-do
A signature transaction completes. On its next pass the agent calls List Signature Transactions, then Refresh Signature Status so the state it acts on came from the signing provider rather than from a cached record. For each completed transaction it reads Get Signature Transaction for the document list, calls Download File on the executed copy, and hands it to the next system: a renewal date written back to the client record in HubSpot, a copy delivered to the counterparty's contact, an entry added to the obligations tracker. Get Node Path turns the internal identifier into a path a person can read, so the notification in Slack says where the contract went rather than quoting a node ID.
-
Intake filed at the node, not in an inbox
Documents arrive as email attachments in Gmail. The agent reads the client name and document type off the content, calls Search to find the client's existing folder, then List Children and Create Folder to place the year and matter nodes if they are not there yet. Upload File puts the document at the resulting node. Where the client is new and the match is uncertain, the agent does not guess at a folder. It files the document in a holding node and raises the ambiguity as one of the automation exceptions a person clears in a minute.
-
The audit pack that never moved a file
Quarter end arrives. The agent runs Search for the documents matching the audit's criteria, calls Create Collection for the quarter, and Add To Collection for each result. Nothing moves. Every document stays at the node where it was filed, with its version history and its place in the tree intact, while the auditor gets one grouping to work from. Get Collection reads the pack back for the cover sheet, and when the audit closes, Delete Collection removes the grouping without touching a single document.
Human-in-Loop Highlight
Resend Signature Email is the only lever this connector has over a stalled contract, and it points straight at a counterparty's inbox. There is no operation here to start a transaction, none to cancel one, and nothing that explains why a signer went quiet. The agent can see that a general counsel has not signed in nine days; it cannot see that the deal is being renegotiated by phone. So the sweep stops and asks the contract owner in Slack: "Transaction 8814, Meridian master services agreement, 9 days open. Two of three signers complete; Meridian's general counsel has not opened it since the 3rd. Send the signers another reminder email, or leave it alone?" The agent supplies the transaction, the signer states, and the days elapsed. The person supplies the thing the API cannot: whether another email helps this relationship or damages it. The email that cannot be recalled is the one the agent never sends by itself.
Agent Capabilities
28 actionsNodes and Tree
7- List Children Lists what is directly inside a folder, one batch at a time. The walk that lets a flow reconcile a folder against what should be in it.
- Get Node Reads one file or folder.
- Get Node Path Reads where a file or folder sits in the tree, as a readable path. Used so notifications name a location a person recognizes instead of an identifier.
- List Ancestors Walks up the tree from a file or folder towards the root. Used to confirm a document landed under the right client before anything downstream runs.
- Create Folder Creates a folder inside another folder. The building block for generating a client structure from a record.
- Rename Or Move Node Renames a file or folder, moves it to another folder, or both.
- Delete Node Deletes a file or folder. A folder takes everything inside it, so flows list the children and report the count before this runs.
Files
3- Upload File Uploads a file from a URL. Revver needs three calls to do this; the extension makes all of them.
- Download File Downloads a file and stores it in file storage, ready for the next system in the chain.
- List File Versions Lists the versions Revver keeps of a file. Used to show what changed before a document is treated as final.
Search
1- Search Searches the document store. The filter is Revver's own search object, which means a flow can find documents by what is inside them rather than by filename.
Access Links
3- List Access Links Lists the links that let people reach documents without a Revver account. The sweep that finds outside access nobody remembers granting.
- Get Access Link URL Builds the shareable URL for an access link.
- Delete Access Link Removes an access link, so it stops working immediately.
Collections
5- List Collections Lists collections, which group documents without moving them.
- Get Collection Reads one collection with what is in it.
- Create Collection Creates a collection. Adding documents to it does not move them.
- Add To Collection Puts a document into a collection. It stays where it is in the folder tree.
- Delete Collection Deletes a collection. The documents in it are not deleted.
Document Requests
3- List Document Requests Lists the requests asking someone to send documents in. Used to find which intake items are still outstanding.
- Get Document Request Reads one document request and whether it has been answered.
- Delete Document Request Deletes a document request, so its link stops working.
Signatures
4- List Signature Transactions Lists the signature transactions on an account. The sweep that replaces opening the signing tool each morning.
- Get Signature Transaction Reads one signature transaction with its documents and signers.
- Refresh Signature Status Asks Revver to re-read the status of signature transactions from the signing provider, so a decision is made on current state.
- Resend Signature Email Emails the signers again about a transaction they have not finished. This reaches a counterparty and cannot be recalled, which is why this page's human gate sits here.
Account
2- Get Current User Reads the user the credentials sign in as. Useful as a connection check, since it needs no identifiers.
- List Notifications Reads the in-app notification inbox: what has been shared, requested, or completed.
Frequently Asked Questions
What can FlowRunner do with Revver?
FlowRunner agents can run List Children, Get Node, and Get Node Path in Revver, plus 25 more actions.
Does connecting Revver to FlowRunner require OAuth?
No. Revver connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Revver trigger a FlowRunner workflow automatically?
Revver doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Storage integrations
Start building with Revver
Free plan, no card required. Connect in minutes.