--- title: "Couchdrop Integration" description: "Couchdrop is a cloud SFTP and managed file transfer platform that mounts S3, SFTP, Dropbox, SharePoint, Box, and Azure into one virtual filesystem. Agents move and share files, provision scoped SFTP users and groups, manage automations, and react the moment a partner drops a file." url: https://flowrunner.ai/integrations/couchdrop date_modified: 2026-09-04T14:07:24-07:00 --- # Couchdrop [Storage](https://flowrunner.ai/integrations/category/storage) Couchdrop is a cloud SFTP and managed file transfer platform that mounts S3, SFTP, Dropbox, SharePoint, Box, and Azure into one virtual filesystem. Agents move and share files, provision scoped SFTP users and groups, manage automations, and react the moment a partner drops a file. 1 trigger · 44 actions · API key · available [Couchdrop website](https://couchdrop.io/) · [Platform Documentation](https://developers.couchdrop.io/llms-full.txt) · Capability data verified 2026-08-13 1. On File Event fires the moment a supplier drops a file into their SFTP folder 2. Get File Details reads the size, type, and modification time of what landed 3. Agent checks the name and size against what this supplier's nightly delivery should look like 4. List Files on the dated archive path confirms this is not a duplicate resend 5. Move File puts the delivery on the archive path the downstream system reads 6. Agent posts the outcome to the operations channel with the supplier and the destination path 7. When the drop is malformed, the agent asks the ops owner whether to run the repair automation against that folder instead of running it on its own ## What This Integration Enables Couchdrop is for teams whose partners will never stop using SFTP and whose own stack has already moved on. It mounts S3, SFTP, Dropbox, SharePoint, Box, and Azure into one virtual filesystem, so a supplier keeps sending files the way they have sent them for twenty years while your team keeps working in the storage it actually chose. The shape of the connector says the same thing: only a handful of its operations touch a file at all. The rest are users, groups, folder permissions, shared links, shortcuts, and automations. This is an access administration surface, not a drive. That is precisely the surface that goes wrong quietly. Agents can provision a scoped SFTP account from a supplier record, create a folder shortcut so one delivery path appears in two places, set a share to expire, and answer audit questions from the event log. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline decides which of those an agent finishes alone and which one it hands to a person, because in a file transfer platform the damage is rarely a bad file. It is a permission granted to the wrong account, or a job that ran against real partner data. ### Without FlowRunner **Accounts built by hand**: Every new supplier means somebody creating an SFTP user, a home folder, and a permission set from a ticket **Links that outlive the delivery**: A share made for one file stays live long after the file stopped mattering **Audit answered from memory**: "Who downloaded that file, and when" gets answered by asking around ### With FlowRunner **Provisioning driven by a record**: The supplier record drives the group, the user, and the folder scope, in one pass **Links with an end date**: Shares are created with a password and an expiry, and withdrawn when the delivery closes **Audit answered from the log**: Get Audit Events turns the question into a query with times and names attached ## Use Case Scenarios ### The delivery gets met where it lands A supplier uploads their nightly manifest over SFTP. On File Event fires immediately, so nothing waits for a polling window. The agent calls Get File Details to read the size and timestamp, compares them against the shape this supplier's file usually has, and calls List Files on the dated archive path to be sure last night's file is not being resent. Move File puts the delivery where the downstream reader expects it, and the agent posts a line to the operations channel in [Slack](https://flowrunner.ai/integrations/slack) naming the supplier and the path. Because the destination path is mounted on [Amazon S3 / Cloud Storage](https://flowrunner.ai/integrations/s3) or [SharePoint](https://flowrunner.ai/integrations/sharepoint), the file is already in the system of record by the time anyone reads the notification. ### Supplier onboarding as one pass instead of a ticket A new supplier record is approved upstream. The agent calls Create Group for the supplier's tier, Create Folder for their home directory, and Create Or Update User to make an account rooted in that folder. Set Folder Permission grants the exact rights that tier is allowed and nothing more, Set Folder Properties turns on the upload portal and delivery notifications for that folder, and Invite User sends the supplier an invitation so they choose their own password rather than receiving one over email. List Folder Permissions reads the result back so the record shows what was actually granted. ### The delivery that did not arrive Each morning the agent calls Get Audit Events for the overnight window and compares the transfers it finds against the list of partners expected to deliver. Silence is the interesting case. For every partner whose file never appeared, the agent gathers the last successful transfer time and the account's current state with List Users, then raises the gap as an exception in [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams) with enough detail for someone to make a call. Nothing is retried, nothing is escalated to the partner automatically. The agent found the missing thing; a person decides what to do about a partner relationship. ## Human-in-Loop Highlight Trigger Event Automation is the operation with no rehearsal in it. An event automation is a stored set of actions, and triggering one runs those actions for real against a path you name, on live partner data, with no preview and no undo. So when a supplier's drop arrives malformed and the repair automation is the obvious next move, the agent does not take it. It assembles the case and asks the ops owner in Slack: "Northline's 02:14 delivery landed at 4 KB against a usual 2.1 MB and failed validation. The archive-repair automation would move the partial file to quarantine and re-request the drop. Run it against /partners/northline/inbound, or leave it for the morning shift?" The agent has already read the file details, checked the archive for a duplicate, and pulled the partner's recent transfer history into the same message. The judgment about running a real job against a live partner folder stays with the person who owns that relationship. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 44 actions ### Files and Folders 7 - **List Files** Lists the files and folders at a path in the Couchdrop virtual filesystem. The starting point for reconciling what a partner sent against what was expected. - **Get File Details** Reads the size, modification time, and type of one file or folder. Used to validate a delivery before anything downstream touches it. - **Download File** Downloads a file from Couchdrop into flow file storage, so a later step can parse or forward it. - **Upload File** Uploads a file from a URL into Couchdrop, landing on whatever storage the destination path is mounted on. - **Move File** Moves or renames a file. Couchdrop treats both as the same operation, which is what makes dated archive paths cheap to maintain. - **Delete File** Deletes a file or folder from the storage it lives on. This cannot be undone from here, so cleanup flows list first and delete second. - **Create Folder** Creates a folder at a path in the virtual filesystem. Used when a new partner or a new period needs its own space. ### Users 5 - **List Users** Lists the users on the account with their home folder and permission mode. Used to audit who can reach what. - **Create Or Update User** Creates a user, or changes one that already exists. Supply the identifier to change a username. - **Invite User** Creates a user and emails them an invitation to set their own password, which keeps credentials out of the workflow. - **Send Password Reset** Emails a user a link to reset their password. Used when a partner contact changes without a full reprovision. - **Delete User** Deletes a user. Their files stay where they are; only the account goes. ### Groups 6 - **List Groups** Lists the user groups on the account. - **Get Group** Reads one group by its identifier. - **List Group Members** Lists the users in a group. Used to confirm a tier's membership before a permission change. - **Create Group** Creates a user group, so access is granted by tier rather than one account at a time. - **Update Group** Renames a group or changes what its members are allowed to do. - **Delete Group** Deletes a group. Its members keep their own accounts. ### Folder Permissions and Properties 5 - **List Folder Permissions** Lists the per-user permissions granted on folders. The read that answers "who can reach this path". - **Set Folder Permission** Grants one user specific rights on a folder. Advanced permissions must be enabled on that folder first. - **Delete Folder Permission** Removes one permission grant. The folder and its files are untouched. - **List Folder Properties** Lists the folders that carry settings such as an upload portal or notifications. - **Set Folder Properties** Sets a folder's upload portal, notifications, and whether advanced permissions apply to it. ### Shared Links 4 - **List Shared Links** Lists the links that give people outside the organization access to a file or folder. The sweep that finds shares nobody remembers creating. - **Create Shared Link** Creates a link to a file or folder for someone outside the organization. Set an expiry and a password. - **Update Shared Link** Changes an existing shared link: what it points at, when it expires, or its password. - **Delete Shared Link** Removes a shared link, so it stops working immediately. ### Shortcuts 4 - **List Shortcuts** Lists the shortcuts that make a folder appear in a second place in the filesystem. - **Create Shortcut** Makes a folder appear at a second path without moving or copying anything. - **Update Shortcut** Repoints an existing shortcut. Both paths are required, as the API replaces the pair. - **Delete Shortcut** Removes a shortcut. The folder it pointed at is untouched. ### Event Automations 5 - **List Event Automations** Lists the automations that run when a file event matches their conditions. - **Get Event Automation** Reads one event automation with its conditions and actions. - **Create Or Update Event Automation** Creates an automation that runs when a file event matches, or changes one that exists. - **Trigger Event Automation** Runs an event automation now, against a path you name. Its actions really happen, which is why this page's human gate sits here. - **Delete Event Automation** Deletes an event automation. ### Scheduled Automations 5 - **List Scheduled Automations** Lists the automations that run on a schedule rather than on an event. - **Get Scheduled Automation** Reads one scheduled automation with its schedule, conditions, and actions. - **Create Or Update Scheduled Automation** Creates an automation that runs on a schedule, or changes one that exists. - **Trigger Scheduled Automation** Runs a scheduled automation now instead of waiting for its next run. Its actions really happen. - **Delete Scheduled Automation** Deletes a scheduled automation. ### Account and Audit 3 - **Get Account** Reads the account the token belongs to. Useful as a connection check, since it needs no identifiers. - **List Storage Connections** Lists the external storage the account has mounted, such as S3, SFTP, or SharePoint. - **Get Audit Events** Reads the audit log: transfers, sign-ins, admin changes, and automation runs, with filters. The operation that turns "who touched this file" into a query. ## Triggers 1 triggers ### Event Triggers 1 - **On File Event** Fires when a file is uploaded, downloaded, renamed, or deleted anywhere the automation is allowed to watch. This is what lets a workflow meet a partner's delivery at the moment it lands rather than at the next polling interval, and it is equally useful for noticing a deletion nobody expected. ## Frequently Asked Questions ### What can FlowRunner do with Couchdrop? FlowRunner agents can run List Files, Get File Details, and Download File in Couchdrop, plus 41 more actions. ### Does connecting Couchdrop to FlowRunner require OAuth? No. Couchdrop connects to FlowRunner with an API key, no OAuth flow required. ### Can Couchdrop trigger a FlowRunner workflow automatically? Yes. Couchdrop supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Couchdrop?** This integration exposes Couchdrop to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/couchdrop. Site index: https://flowrunner.ai/llms.txt