Automate file workflows between Couchdrop and Make

Couchdrop connects with Make.com in two directions: it can send files into a Make.com scenario, or Make.com can call Couchdrop actions from inside a scenario.

For file intake, Couchdrop links a folder to a Make.com custom webhook. When a file is uploaded into that folder, Couchdrop automatically sends the file to the connected Make.com scenario, allowing the scenario to continue with routing, notifications, transformation, storage, or application updates.

For operational workflows, Make.com can also use the Couchdrop module to upload files into Couchdrop, work with files and folders through the Filesystem API, and call management actions such as user and permission administration.

Make.com has a 5 MB file size limit when receiving files from Couchdrop, so webhook-based delivery is best suited to lightweight file-triggered automations.

• Send files from Couchdrop into Make.com scenarios using a custom webhook
• Trigger Make.com automations when files arrive in a linked Couchdrop folder
• Receive files through Couchdrop using SFTP, FTP, and other managed transfer protocols
• Upload files into Couchdrop from Make.com scenarios
• List, download, rename, delete, and create files or folders through Couchdrop filesystem actions
• Run Couchdrop management actions from Make.com using a Couchdrop API token

1. In Make.com, create a new scenario.
2. Add a Custom Webhook as the scenario trigger.
3. Name the webhook and copy the generated Webhook URL.
4. In Couchdrop, add a new outbound connection and select Make.com.
5. Enter a name for the integration.
6. Choose the Couchdrop folder that will send uploaded files to Make.com.
7. Paste the Make.com Webhook URL and save the connection.
8. Upload a test file into the linked Couchdrop folder to confirm it is sent to your Make.com scenario.
9. To run Couchdrop actions from Make.com, add the Couchdrop module to a scenario and connect it with a Couchdrop API token from Admin → API Tokens.