The Webhook Logs show the results of webhook calls made from your Files.com site to other systems.

Each entry records the file that triggered the webhook, the folder where the file was located (which contains the configuration for this webhook), and the URL that the webhook called.

The log also records the HTTP request method (for example, POST or GET), the sent HTTP request headers, and the returned HTTP response code and response message from the remote API.

Access and Workspace Scope

Site Administrators can view Webhook Logs and export records for a selected Workspace or the whole site. Workspace Administrators can view and export only the records for their selected Workspace. This lets a team's administrator troubleshoot webhook delivery within the area they administer.

An export for a named Workspace includes only records whose file path is that Workspace's root folder or one of its descendants. An export for the Default Workspace excludes records from named Workspaces. A site-wide export includes records across the site, including the Default Workspace and named Workspaces, so selecting the Default Workspace is different from requesting a site-wide export.

Each export keeps the scope used to create it. Switching Workspaces does not change that export's records or make its results available in the new Workspace. After switching, create a new export for the selected Workspace, even if you administer both Workspaces.

Retention

We retain these logs indefinitely as long as the site remains active.

Webhook failure records used for retries have a separate three-day retention period and can be replaced or removed earlier as retries are processed. Their removal does not remove the corresponding Webhook Logs. Generated notification exports and their CSV files have a 30-day lifetime.