Notifications

Notifications let you react to Files.com activity by sending messages or events to other tools. Use them when you need awareness, an audit trail, or automation outside Files.com without polling. Choose the notification feature that best meets your needs, as each offers unique capabilities.

Choosing a Notification Feature

Use Email notifications when a human should read and act. This fits approvals, exceptions, and “someone should know” alerts.

Use Webhooks when a system should react. This fits triggering workflows, syncing metadata, or kicking off downstream processing.

Use Slack webhooks when you want lightweight visibility in a team channel. This fits operational awareness without building an integration.

Use Microsoft Teams when your org’s default alerting surface is Teams. Treat it like Slack: human-visible, low-friction notifications.

Use Amazon SNS when you want Files.com events to land inside AWS for fan-out. This fits routing to SQS, Lambda, or other SNS subscribers.

Use Google Cloud Pub/Sub when you want Files.com events to land inside GCP. This fits routing to Cloud Functions, Dataflow, or other Pub/Sub subscribers.

Emails from Files.com

Several Files.com features generate email messages. Refer to Emails from Files.com when you need to control or troubleshoot outbound mail (sender settings, deliverability, unsubscribes). Start here when “email notifications aren’t arriving.”