Celigo Storage is a built-in file management resource in integrator.io that lets you upload, browse, and manage files and folders without configuring external storage infrastructure. Use it to store and organize reference files for your MCP servers — policy documents, product schemas, mapping templates, and similar materials — all without leaving integrator.io.
This article explains what Celigo Storage is, how it works, and when to use it. To start managing files, see Create folders and upload files in integrator.io.
Select Resources > File storage to start working with Celigo Storage.
Feature availability:
- What you can see and do in Celigo Storage depends on your role: admins have full access to all content, while Manage all, Monitor all, and Custom users work within integration system folders. Non-admin users can also use Celigo Storage inside flows by creating a Celigo APIs connection with the Integration access scope. See also Restrict an API token to specific Celigo Storage paths.
-
This feature is only available to accounts working in the multiple-environment structure. With this structure, each environment keeps its own isolated resources; in the legacy Production and Sandbox model, the two environments shared some resources. If you see the following Production and Sandbox option, your account has not yet migrated to the multiple-environment structure.
Celigo Storage organizes files in folders. You can create folders in the root directory or within any existing folder, with unlimited nesting depth. Each file displays its name (including extension), size, last modified date, and an optional description. Folder and file names within the same folder must be unique.
All files and folders have stable internal IDs. Moving or renaming an item doesn't break references to it from MCP server configurations or from flow exports and imports.
In addition to the folders you create, Celigo Storage automatically creates a system folder for each integration and workspace in your account. System folders give non-admin users role-based access to storage. These folders are managed by the platform - they can't be deleted, moved, copied, or renamed.
Role-based access
What each user sees and can do on the File storage page depends on their role:
- Admin — Full access to all storage content, including user-created folders at the root and all system folders.
- Manage all — Full access (create, edit, and delete) inside every integration system folder.
- Monitor all — Read-only access (browse and download) across all integration system folders. Monitor all users don’t see root-level user-created content.
- Custom — See only the system folders for the integrations their role grants access to. Users with Manage access to an integration get full access inside its system folder; users with Monitor access get read-only access.
Search results are role-scoped — users only see the files and folders their role gives them access to.
Each account has a single file storage allowance based on its plan tier, shared across all environments. At minimum, all accounts receive 1 GB. Professional accounts get 100GB and Enterprise accounts, 200GB. Add-on storage bundles are available to increase the total allowance — your total allowance is your plan tier’s base allowance plus any purchased add-on bundles. You can view current usage and request additional storage on the Subscription page (Account > Subscription). Storage usage is account-wide — not split per environment. Usage updates in real time.
Caution
Deleted items sitting in your recycle bin still count toward your storage limit until they are permanently purged (either manually or automatically). Simply deleting a file won't immediately free up space.
The platform-wide audit log (Account > My profile > Audit log) automatically tracks all state-changing actions on files and folders, including uploads, renames, moves, copies, deletions, restorations, and purges. Storage entries are categorized as File and Folder resource types alongside other platform resources. Read-only operations, such as browsing files or downloading them, are not logged.
Use Celigo Storage for files that support your integration workflows but do not need to leave the platform. For example, you can use Celigo Storage for the following:
Flow-to-flow file staging - Stage and transfer files directly between flows without the overhead of external infrastructure. Leverage Celigo Storage as a source, destination, or lookup component through the Celigo APIs connector. It’s ideal for routing B2B EDI documents, aggregating data across multi-page flows, and handing off files between processes.
AI & agent reference material - Store persistent reference documents—such as policy files, product schemas, and mapping templates—for AI agents and MCP servers to access across multiple runs.
Team collaboration - Centralize and organize integration artifacts that multiple team members need to access.
Keep using external file providers (Amazon S3, Azure Blob, SFTP, Google Cloud Storage, etc.) when files genuinely need to reach external systems — data lakes, trading partner delivery, archival destinations, or any destination outside integrator.io.
Why do deleted files still show in my storage usage? Deleted files go to the recycle bin and remain in storage until they're permanently purged — either automatically by the platform's retention policy or manually by an Admin. To free space immediately, permanently purge items from the recycle bin (Resources > Recycle bin).
Does renaming or moving a file break MCP or flow references to it? No. References use stable internal IDs rather than file paths. Renaming or moving a file or folder will not break existing MCP server references. Similarly, export and import references in flows rely on these unique IDs and continue to function after a rename or move.
What happens to my MCP server references if I delete a referenced file? When you delete a file or folder that an MCP server references, the system automatically removes that reference from the MCP server configuration. The MCP server continues to work with its remaining references. The delete confirmation dialog shows you which MCP servers reference the item before you confirm.
What happens to my flows if I delete a referenced folder? Flow exports, imports, and lookups reference folders, not individual files, and the reference remains in the flow after deletion. On the next scheduled or manual run, a step that uses a folder ID reference fails. A step that uses a relative path reference adapts: an import recreates the missing path, while an export or lookup fails if the source path no longer exists.
What happens if I go over my storage allowance? By default, uploads are not blocked when you exceed your allowance - usage continues normally. On accounts where storage overage is disabled and you exceed your account limit, new uploads are blocked, and a "Storage allowance reached" banner appears on the File storage page. You can still view, download, and manage your current files until you free up space. To increase your allowance, purchase an add-on storage bundle.