Articles in this section

Celigo Storage activity log

The storage activity log records what happened to the files and folders in Celigo Storage — who did it, when, and from where. It covers every source that can reach storage, so you can answer "who deleted this file" or "did my partner collect the order file" without knowing which surface the operation came through. Reads are included: downloading a file is recorded, not only changing one.

Activity log and audit log

integrator.io keeps two separate logs, and each owns a different kind of event. An operation is recorded in one or the other, never both.

Log Records Where to find it
Storage activity log Operations on files and folders, from every source, including reads Resources > File storage
Platform audit log Configuration changes, including file server and account settings Account > Audit log

Sources

Every entry records the source the operation arrived through. Use the source to tell a person's action from a machine's.

  • UI — The File storage page.
  • API — The storage REST API, and flow steps that read or write storage files.
  • CLI — The command-line interface.
  • MCP — A file an MCP server publishes as a resource, or the Celigo MCP server.
  • Ora — A file read or written through Ora.
  • File server — An account-holder connected over SFTP. The actor is the partner account name.
  • System — An operation integrator.io performed itself, such as creating or deleting the folder that belongs to an integration. The user is whoever's action triggered it.

Note: A flow's entries show the source as API and the account owner as the user. The entry does not identify which flow ran the operation.

Actions

Each entry carries one action. The action never says whether the item was a file or a folder — the log shows that separately — so Create always means a folder, because files are uploaded rather than created.

Action Means
Login A sign-in attempt on a file server account. File server only. A failed attempt is recorded and marked in the log.
Download Bytes read from a file, from any source — a browser download, an SFTP get, a flow reading a file, or an API fetch.
Preview A file rendered in the Storage UI without a copy being taken.
Query A storage query execution.
Upload File bytes written. Replacing an existing file is an Upload that records the overwrite and the previous size.
Create A folder created.
Update Metadata edited in place, such as a description. A rename is recorded as an Update, with the previous and new name.
Move A file or folder moved to another folder.
Copy A file copied. The entry is recorded on the new file.
Merge A folder merged into another. Recorded once, on the destination folder.
Delete Sent to the recycle bin.
Restore Brought back from the recycle bin.
Purge Permanently removed.

What an entry contains

  • Timestamp — When the operation happened.
  • User — Who performed it. For a file server operation, the partner account name.
  • Source — Where it came from.
  • Action — What was done.
  • Target — The file or folder, shown as its name and the name of the folder holding it. The entry is tied to the item's internal ID, so it stays accurate after a rename or a move. An item that has been purged shows its ID instead of a name.
  • Source IP — The caller's address, where the source has one. Always present for file server activity.
  • Details — Information specific to the action, shown as JSON. A download records the file size and how long its link stays valid; an overwrite records the previous size; a rename records the previous and new name; a bulk move marks each entry as part of a bulk operation; a copy records the original file's ID; a query records the statement that ran.

One entry per action

The log records what you did, not the work integrator.io did to carry it out.

  • Renaming or moving a folder is one entry, however many items are inside it.
  • Deleting a folder is one entry on the folder.
  • Downloading a folder as a .zip file is one entry on the folder, recording how many files it held and their total size. The files inside get no entries of their own.
  • A bulk move is an exception: it records one Move entry for each item moved, each marked as part of a bulk operation.

What is not recorded

  • Listings and searches — Browsing a folder or searching for a file leaves no entry, on any source.
  • Refused operations — An operation that permissions blocked leaves no entry. The log records what happened, not what was attempted.
  • Operations that failed partway — An abandoned upload or a rolled-back copy writes nothing.
  • Which files a query read — A query is one entry holding the statement, with no target, so filtering by a file name does not return the queries that read it.
  • Whether downloaded bytes arrived — A Download entry means a download link was issued. The log cannot tell whether the file was then fetched.

Who can see activity

Access follows the same folder access you have elsewhere in Celigo Storage. You see activity for the folders you can see, and an API token restricted to specific storage paths returns activity only for those paths and everything beneath them. File server credentials cannot read the log.

How long activity is kept

Activity is retained for the same period as your platform audit log, set by your license. Retention is the same for every source and every action.

License Retention
Standard 1 year
Professional 2 years
Enterprise 3 years

View and filter activity

  1. Go to Resources, and then select File storage.
  2. Open the activity log.
  3. Narrow the results using the filters. You can filter by action, user, source, and time range, and sort by time. The time filter starts at the last year. A filter is shaded while it is applied, including the starting time range.
  4. To find a specific item, filter by name. The name filter searches the results already loaded rather than the whole log, so narrow by action, user, source, or time first.
  5. To see everything recorded for one item, find it on the File storage page, select Actions, and then select View activity. On a folder this shows activity on the folder itself, not on the files inside it.
  6. To keep a copy, select Download. The file is a CSV and carries the filters you have applied.

Related articles