Many automations hit the same wall: that legacy system, database or file server with no modern API. Floogos adds nodes for exactly that: MongoDB for document databases, SSH to run commands and move files over a server, and FTP/SFTP for transfers. With them, virtually any piece of your infrastructure fits into a workflow. Let's see how.
MongoDB: operate your document database
The MongoDB node runs the usual operations on your collections:
- find / findOne to read documents with JSON filters
- insert, update and delete to modify data
- aggregate for pipelines and count for counts
- Connect via connection string or host/credentials
💡 Tip: use find's JSON filter to fetch only what you need. Less data per step = faster workflows.
SSH: run commands and move files
The SSH node gives you access to your servers from the workflow:
- execute to launch remote commands (scripts, maintenance tasks)
- upload / download to transfer files over SFTP
- list and delete to manage remote files
- Authentication by password or private key (PEM)
💡 Tip: prefer a private key over a password for automated SSH connections; it's more secure and won't expire under password policies.
FTP / SFTP: transfer files
For classic file exchanges (very common in B2B integrations):
- list, upload, download, delete and rename
- Supports FTP and SFTP depending on your server
- Ideal for picking up or dropping files in agreed folders
- Fits batch import/export processes
💡 Tip: combine FTP with a scheduled trigger to pick up files every so often and process them automatically.
And for everything else, the HTTP node
If a system has no dedicated node but does have an API, the HTTP node covers it:
- Call any REST API or webhook
- Configurable headers, authentication and body
- Resolves variables from previous steps in the request
- The safety net that leaves almost nothing out
💡 Tip: between dedicated nodes (MongoDB/SSH/FTP) and the HTTP node, it's rare to find a system you can't integrate.
Combine them into a real flow
The power shows when you chain them into one process:
- Pick up a file over FTP, transform it and store it in MongoDB
- Run a script over SSH after processing the data
- Notify the result by email or chat
- All with traces and insights per run
💡 Tip: start with the manual process you repeat most (that weekly export/import) and turn it into a workflow.
Checklist to integrate your infrastructure
Frequently asked questions
What operations does the MongoDB node support?
find, findOne, insert, update, delete, aggregate and count. You connect via connection string or host and credentials, and specify the collection and the JSON filter/document.
Can I run commands on my server with SSH?
Yes. The SSH node allows execute for remote commands, plus upload/download/list/delete over SFTP, with password or private-key authentication.
What's the difference between FTP and SFTP?
FTP is the classic transfer protocol; SFTP runs over SSH and is encrypted. The node supports both; choose based on what your server offers.
What if my system has no dedicated node?
If it exposes an API, the HTTP node covers it. Between dedicated nodes and HTTP, virtually any system can fit into a workflow.
The best automations leave no islands: they also connect those "hard" systems with no modern API. With MongoDB, SSH and FTP/SFTP —and the HTTP node for the rest— Floogos lets you integrate databases, servers and files into the same workflow as your cloud apps. Stop moving files and running scripts by hand; put it all into a flow.