Files.com sends real-time notifications about file activity to a Microsoft Teams channel through an incoming webhook. For background on Teams webhooks, see Microsoft's documentation on Teams connectors and webhooks.

How Microsoft Teams Notifications Work

Sending messages to Microsoft Teams from Files.com requires an incoming webhook URL associated with a Teams Workflow, which is configured in Microsoft Teams.

When you create the Microsoft Teams notification in your Files.com site, you provide the URL of the webhook for the Teams Workflow that receives the messages about file activity.

When matching file activity happens in your folder, a message is sent to Microsoft Teams with the details. The settings on the Teams Workflow determine where and how the message is displayed.

What is Included in Microsoft Teams Notifications From Files.com

Files.com sends a Microsoft Teams message containing an Adaptive Card, in JSON format. The Adaptive Card includes a readable summary of the relevant file activity, like "Downloaded /Folder/example.pdf ", along with the associated user's name and the file's size.

Creation messages identify the resulting file or folder path, including files produced by TransformScript, document or image conversion, ad hoc GPG encryption or decryption, and ZIP extraction. Copy and move messages include both the original and resulting paths. Moving a file or folder to a new name within the same parent folder appears as a rename.

Messages about a folder rather than a file will not include the file size because folders do not have a file size. Operations performed using a site-wide API key are not associated with a user, so no username is included for those actions.

Timing of Microsoft Teams Messages from Files.com

Microsoft Teams Notifications send messages to your Teams channels within seconds of Files.com recording matching folder activity. For changes made directly on remote storage, this follows detection by a Remote Metadata Index scan.

Microsoft Teams Configuration

The Workflows app in Microsoft Teams lets you create automated workflows that can receive HTTP requests through a webhook URL. When the webhook triggers, the workflow posts a message to your Teams channel, formatted as an Adaptive Card. Adaptive Cards are JSON-based UI snippets that render interactive content in Teams chats and channels.

Open the Workflows app and create a new flow. Use the template for "Post to a channel when a webhook request is received." Add a name for your flow, then choose the Team and Channel where you want messages to be posted. You must be a member or owner of the channel to add a workflow to it.

Once the workflow is created, copy the generated URL for setting up your Microsoft Teams Notification in Files.com. Keep this URL secure; anyone with this link can post messages to your channel.

Required Permissions for Microsoft Teams Workflows

Some organizations restrict the use of Power Automate/Workflows. You may need to ask your IT department to allow the "Workflows" app.

Teams Workflow Owners and Co-Owners

Workflows are linked only to specific Teams users (referred to as owners of the workflow) and not to a Teams team or channel. Workflows can become orphan flows in the absence of an owner if no co-owners are assigned. To maintain continuity in the business process automated by the flow, admins can add one or more co-owners and grant them full control over the workflow.

Creating a Microsoft Teams Notification

Before you begin, configure a Microsoft Teams webhook URL for the channel where you want notifications to be sent.

Only users with administrator-level access to your site, Workspace or the folder can configure Microsoft Teams notifications for a folder.

Add the new Microsoft Teams notification in your Files.com site, supplying the complete URL generated by your Teams workflow. The URL must meet the webhook URL requirements below.

You must choose which folder's activity will generate messages for the Teams Notification.

Activity in the folder and its subfolders is included by default; you can change this to only generate messages for actions occurring directly in the selected folder. On a Remote Server Mount, remote creations and deletions also generate matching notifications when Remote Metadata Index detects them in scans after its initial baseline.

By default, notifications are for any file or folder action (create, read, update, delete, move, or copy) within the configured folder. You can limit which actions generate notifications.

There is no waiting period after enabling the new notification in your Files.com site; any matching activity will immediately generate messages.

Webhook URL Requirements

Files.com sends notifications from its servers, so the webhook destination must be reachable over the public internet. The URL must use HTTP or HTTPS, resolve to an allowed public IP address, and use port 80, 443, or a port above 1024. These are the same destination rules used for Webhooks. Private, loopback, and link-local addresses are not permitted, even if the URL works from your own computer or network.

When you create a notification or change its URL or selected file actions, Files.com validates the destination before saving. This applies through the web interface, API, CLI, and SDKs in every Workspace. A malformed URL, disallowed port or address, or hostname that cannot resolve prevents saving. If an update fails validation, the previously saved configuration remains intact. Check that you copied the complete workflow URL and that its hostname resolves publicly.

The destination check does not send a test message, require a successful HTTP response, or confirm that Microsoft issued the URL. A successful save therefore does not establish that the Teams workflow will post messages to your channel. To confirm delivery, perform one of the selected file actions in the configured folder and check for its message in the intended Teams channel.

Files.com checks the destination again when sending each notification. If the address no longer meets the destination rules, Files.com does not send the message to it.

Microsoft Teams Rate Limits

If more than 4 messages are sent to the Microsoft Teams Workflow in a second, the client connection is throttled until the window refreshes for the duration of the fixed rate.

A Microsoft Teams Notification tied to a folder with extreme activity might exceed the rate limiting threshold. Files.com cannot send "digest" messages to combine multiple operations in a single message, so operating on many files at once will generate many messages quickly.

Repeated throttling usually means the notification is too broad to be actionable. Narrow the folder scope or the list of file operations so the channel carries useful activity instead of a constant stream.

Common Failure Patterns

When a Microsoft Teams Notification stops sending messages to your Teams channel, there are common things to check.

As of May 18, 2026, Microsoft deprecated legacy Teams webhook URLs. If your URL was configured before then, and stopped working after that date, you must set up your webhook within Microsoft Teams using the Workflows app. Update your Microsoft Teams Notification with the new webhook URL.

Use curl to send a test message directly to the webhook URL. If the message appears, the Teams workflow accepted that request. This helps isolate problems with the workflow, but delivery from Files.com still depends on the notification settings and destination checks.

If the test message did not appear, check for configuration issues:

Check the Team channel. If the channel the workflow posts to was deleted or renamed, notification messages cannot be posted.
Make sure the workflow was not disabled within Microsoft Teams.
Verify that the Teams user who configured the workflow is still a member of the organization.
Ensure that the owner or co-owner of the Workflow has access to the channel.

If the test message appears in your Teams channel, check the settings on your Microsoft Teams Notification and make sure that the correct folder scope (just the folder vs the folder tree) and the list of selected file operations is correct. Check that the History listing for your folder shows activity that should have triggered the notification.