Automation & Flow

A file workflow needs a way to move or process files, a way to check the result, and a way to tell someone when attention is needed. Files.com provides separate features for each job, so a successful transfer and a complete, valid delivery can be monitored independently.

Start with the action your workflow needs. Use Automations for triggered file actions, Sync for folder replication, and TransformScript to reshape file contents. Add Expectations to check deliveries, then choose Notifications for file activity or Event Channels for operational outcomes. Automated Workflows explains decisions that span these features, including Syncs & Automations.

When building several flows or replacing an MFT platform, use Managed File Transfer first to choose production and test environments, Workspace ownership, and the handoff into production. A single straightforward flow can run in the Default Workspace.

Automations

Automations run file actions on a schedule, in response to file activity, or when an external system calls a webhook. A v1 Automation performs one action, such as copying incoming invoices to several departments, moving files into an archive, importing a file from a URL, or starting a Sync. Its source patterns select files, and its destination settings control their names and locations.

Automations v2 adds connected steps, branches, transformations, and error paths within one run. It is an opt-in early beta and is not recommended for business-critical production workflows. Start with its beta access guidance before building or migrating a workflow.

Sync

Use Sync when one folder needs to be replicated to another. A Sync compares the source and destination, transfers new or different-size files, and can delete source files after successful transfer. It works with Files.com folders, Remote Servers, and child sites.

Choose a Sync's trigger and file filters when creating it. Use an Automation when files need renaming, several destinations, or processing beyond replication; an Automation can also start a Sync as part of that work.

TransformScript

TransformScript reads structured file data and produces a new shape or format, such as converting a partner's CSV into the JSON your application accepts. It can normalize values, filter records, and map EDI or HL7 documents.

Run a script with the Transform File action for a one-off conversion, or in an Automations v2 Transform node as part of a workflow. Expectations also use TransformScript for Content Validation, where the script returns a validation result rather than a new file.

Expectations

Expectations check whether a delivery meets your requirements: which files arrived, their count and size, and optionally their contents. A delivery window defines when files count toward the evaluation. Scheduled windows can detect a missing delivery even when no file activity occurred.

Each Evaluation records the result and the criteria that failed. A failed scheduled window opens an Incident for investigation. Expectations monitor deliveries; they do not move or repair the files. Use them alongside the Automation or Sync that performs the transfer.

Notifications

Notifications report file and folder activity such as uploads, downloads, moves, copies, and deletions. Use email notifications when people need a digest of activity, or webhooks, Slack, Teams, SNS, or Pub/Sub when another system needs to receive the event. Activity performed directly on a Remote Server outside Files.com does not trigger these notifications.

Event Channels

Event Channels report operational outcomes, including Sync and Automation runs, Expectation evaluations and incidents, and security or integration events. Use them to route failures to an operations team or signal successful completion to a downstream system. Subscriptions select the events, Targets select the destinations, and Delivery Attempts show whether messages arrived.

AI Tasks

Use AI Tasks for unattended work that needs interpretation, such as reviewing a document or writing an assessment of permissions. Use fixed rules in Automations, TransformScript, or Expectations when the check can be expressed precisely. For example, a scheduled AI Task can write a permissions review to an admin folder, and a Notification can tell the team that the report is ready.

Schedules

Schedules let Automations, Syncs, AI Tasks, Expectations, and Scheduled Exports share days and times. Editing the Schedule changes the timing for everything that uses it. A Holiday Calendar supplies your organization's closures when the built-in Holiday Regions do not match.

Secrets

Secrets store credentials and sensitive values with site or Workspace ownership. See the Secrets reference for the available types, visibility rules, and current integration availability.