Targets
A Target is a delivery destination within Event Channels. Targets define where matching events are sent. A single target can be attached to multiple subscriptions, so you can reuse one Slack channel or webhook endpoint across different event routing rules.
On sites without Workspaces, all targets are site-level. On sites with Workspaces, targets are scoped to the workspace where they are created. Workspace Administrators create targets within their workspace for use in their own subscriptions.
Site Administrators in the Default Workspace can enable Apply to All Workspaces on a target, which allows it to receive events from every workspace on the site. Cross-workspace delivery requires both the subscription and every target it routes to have Apply to All Workspaces enabled. Setting it on the target alone is not enough. For email targets, recipients must still be users in the Default Workspace even when the target is set to apply to all workspaces.
Target Types
Files.com supports the following target types with Event Channels. Each target can be reused across multiple subscriptions.
Email targets deliver batched event summaries to one or more users on your site. Multiple Recipient Users can be selected on a single target. The batch interval is configurable between 10 minutes and 24 hours. Recipients do not need to be Site Administrators.
Each subscription's Email Content settings control the subject and message of the emails it generates.
Webhook
Webhook targets deliver a JSON event payload to an HTTPS URL for each matching event. Custom request headers are supported. Webhook targets can optionally use Dedicated IPs, which routes deliveries through a fixed set of IP addresses you can allowlist in your firewall or receiving system.
Slack Webhook
Slack Webhook targets deliver a human-readable message for each matching event. The message content is generated from the event title, summary, and key fields.
Teams Webhook
Teams Webhook targets deliver a human-readable message for each matching event using the same generated content as Slack.
Amazon SNS
Amazon SNS targets publish event payloads to an SNS topic. The target requires a Topic ARN, Access Key ID, Secret Access Key, and Region. Credentials (Access Key ID and Secret Access Key) are not shown after saving and must be re-entered to replace them.
Google Cloud Pub/Sub
Google Cloud Pub/Sub targets publish event payloads to a Pub/Sub topic. The target requires a project ID, topic ID, and Google credentials. For security, the private key inside the credentials is not retrievable after saving. Record it before saving the target.
Folder
Folder targets stream matched events to a destination folder instead of pushing them to an endpoint or service. Use this when the consuming system reads files on its own schedule rather than receiving pushes, or when you want only specific, filtered events instead of everything Log File Streaming would write.
The destination folder can be a folder on Files.com or a folder on a Remote Server Mount. Folder targets write files in JSON or CSV format on a batch interval configurable between 10 minutes and 24 hours. You choose the format when you create the target, and cannot change it afterward. The destination folder and batch interval remain editable.
Files.com writes each file once, as a complete output, at the end of its batch interval, and does not modify it afterward. A file is safe to process as soon as it appears, with no risk of partial or still-changing data. The next interval's events go to a new file.
Files.com names each file events-[delivery attempt ID]-[timestamp].[extension], so you can trace any delivered file back to its own Delivery Attempt record. The timestamp reflects when the file was written, so a system polling the destination folder can order files chronologically and process them in the sequence they arrived.
Notifications use the same target types for folder activity alerts (uploads, downloads, moves, and deletions). Event Channel targets and Notification targets are configured and managed separately.
Delivery Batching
Email and Folder targets batch events together on a configurable schedule between 10 minutes and 24 hours. Email targets deliver a summary to their recipients at the end of each interval. Folder targets write that interval's events to a file in the destination folder. Email target batching is separate from admin email alert batching, which Files.com spaces out automatically, starting at 3 hours and widening the gap to a maximum of 24 hours.
All other target types (webhook, Slack, Teams, SNS, Pub/Sub) deliver one payload per event as events occur.