Cloud Fax Toolkit

Bridge Fax Workflows to the WestFax Cloud.

Connect applications, EHRs, databases, folders, printers, MFPs, and identity systems to WestFax. CFT processes inbound and outbound fax jobs, applies configurable routing rules, and delivers documents to the destinations your workflows require — without rebuilding what already works.

Enterprise deployments are scoped and implemented with WestFax.

Legacy Fax Migration

Replace the Fax Server. Keep Everything Around It.

Legacy fax servers sit at the center of the workflows your teams rely on every day — and replacing one shouldn't mean rebuilding all of them. Cloud Fax Toolkit moves fax transport to the WestFax cloud while those workflows stay exactly as they are. Cut fax boards and analog lines, retire fragile hardware, and gain cloud reliability — without disruption.

  • Save money
    Retire fax boards, analog lines, and server upkeep — move to predictable cloud fax.
  • Save time
    No rebuilding integrations or retraining staff — existing workflows keep running.
Smiling clinician in scrubs sending a fax from a multifunction printer in a bright hospital corridor

Identity & Access

Fax Identity & Access, Centrally Managed.

Connect fax to the identity systems your organization already runs. The Cloud Fax Toolkit provisions users from your directory, authenticates them through your existing SSO, and keeps print- and email-to-fax permissions in step — so access follows each person automatically, with nothing to manage by hand.

Explore identity & access management

Active Directory Synchronization

CFT keeps your WestFax users, groups, and permissions in step with Active Directory on every scheduled sync — your directory stays the source of truth.

  • User & group synchronizationProvision WestFax users straight from your Active Directory security groups, so your directory stays the source of truth.
  • Group-based access & permissionsMap directory groups to the right fax access and permission level by team, site, and role — with pre-sync validation and exempt-admin safeguards.
  • User onboarding & offboardingAs employees join, move, or leave, their fax access follows your directory on every scheduled sync.

Inbound Routing & AutoPrint

Inbound faxes, back to the printer.

The Cloud Fax Toolkit routes incoming faxes to the printers and destinations your staff already use — AutoPrinting each one to the right device by fax line, department, location, or any rule you configure. Your team keeps the familiar “the fax is on the printer” workflow across any brand, with no fax line, no fax board, and no native connector per model.

Getting a fax out of a printer is a separate path — see MFP integration.

Smiling office worker collecting an inbound fax that AutoPrinted to their multifunction printer
  • Route inbound faxes anywhereAutoPrint straight to an MFP, or route by fax line, department, or location — inbound faxes land wherever your workflow needs them, on the rules you configure.
  • Any brand, one cloudRoute inbound faxes to new, legacy, and mixed-brand printers alike — no native connector per model, no analog lines to maintain.
  • The workflow staff already knowFaxes still land on the same device your team walks up to today. AutoPrint sends the ones that need paper to the right printer — and holds the job if it’s briefly offline.
  • Devices stay inside your networkYour MFPs talk to CFT over the local network, and CFT makes the secure, up-to-date connection to WestFax on their behalf — so even older printers that can't meet modern encryption standards are covered, with no device needing its own internet path.

Routing & Workflow Automation

Every Fax, Routed to the Right Place.

CFT is the routing layer between your systems and the WestFax cloud. Every job is mapped to the right fax line, cover sheet, and destination — so inbound and outbound faxes land exactly where your workflows expect them. Routing is configured for your environment and runs automatically, without the legacy fax server in the middle.

Outbound

From your systems to the cloud

CFT accepts outbound jobs from the systems you already run, maps each to the right fax line and cover sheet, and submits it to WestFax for transmission — applying the correct configuration without anyone touching it.

Outbound sources
Watched folders Local directories Network shares UNC paths SQL databases EHRs & business apps MFPs Print workflows Email / internal SMTP
Inbound

From the cloud to where work happens

Every incoming fax is routed by its fax line and delivered as a PDF or TIFF with a custom filename — to one destination or several, exactly where that line needs it on arrival.

Inbound destinations
Local folders Network shares UNC paths Printers via AutoPrint Internal SMTP SQL-connected workflows EHR / document management Multiple destinations
Conditional & rule-based routingRoute differently based on conditions and consistent rules you define.
Multi-destination deliverySend a single inbound fax to several destinations at once.
Custom filenamesName delivered files to match the systems that consume them.
PDF & TIFF deliveryDeliver inbound faxes in the format your downstream systems expect.
Route by
Fax number Department User Device Location Metadata

Inside drop-folder processing

The most common outbound pattern — a system drops a file, and CFT takes it the rest of the way. It runs on the structured fax jobs your systems already produce.

1 Drop A system writes a control file and document to a watched folder.
2 Parse & map CFT validates the job and maps it to the right fax line and cover sheet.
3 Submit The fax goes to the WestFax cloud over a secure API.
4 Automate Receipts, result files, and status updates flow back automatically.
Built for structured fax jobs

CFT processes the documents, control files, and job metadata your EHRs, line-of-business applications, and legacy fax workflows already produce.

Fax Control Language (FCL) Structured control files Document & metadata pairs PDF & TIFF documents Custom implementation formats

Connect internal email workflows

CFT can accept or deliver fax documents through internal SMTP, so applications and users exchange fax jobs without exposing every connected system to an external mail service. It’s one of four distinct ways email and fax meet — here’s how they differ.

Identity Allowed-sender sync Keeps the list of addresses authorized to send Email-to-Fax in step with Active Directory.
Outbound Email-to-fax submission A user emails a document to a fax address and WestFax sends it on as a fax.
Bridge Internal SMTP routing CFT relays fax jobs through your own mail server, keeping the traffic inside your network.
Inbound Fax delivery by email Incoming faxes land in mailboxes through your internal SMTP — not only an external service.

SQL Connectivity

Connect Fax Workflows to SQL.

Use CFT to connect fax processing with the databases and applications your organization already relies on. CFT can exchange job information, processing results, and fax status with local or enterprise SQL environments.

  • Submit fax jobsLet an application or workflow create outbound fax jobs through database-driven processes.
  • Return status & resultsWrite submission, delivery, failure, and completion information back to the connected workflow.
  • Support existing applicationsAdd cloud fax to systems built around SQL — without redesigning the application around a new interface.
  • Local or enterprise SQLDeploy with local SQL or enterprise SQL infrastructure, matched to the availability and scale your environment requires.

Status, Receipts & Results

Keep Applications Informed After Submission.

Transmitting the fax is only half the job. CFT closes the loop — every submission, delivery, and failure is captured and returned to the system that started it, so your applications always know what happened.

Submission acknowledgmentsCFT confirms each job was accepted and queued for transmission, so the originating system knows it was received.
Delivery confirmationsWhen a fax completes, CFT returns a success result your application can record against the original job.
Failure results & reasonsIf a fax fails, CFT captures the failure and its reason so your workflow can flag, retry, or escalate it.
Machine-readable status filesResults are written back as structured files or notifications your downstream systems parse automatically — no manual reconciliation.
Outbound queue processingCFT works outbound jobs as a managed queue, moving each through submission, transmission, and result handling in order.
Retry & exception handlingTransient problems are retried, and exceptions are routed to the success, failure, and notification paths you define.
Results returned to Originating EHR / app Printed receipt File notification Internal email API callback Status file

Deployment Options

Deploy CFT Where Your Workflows Need It.

Cloud Fax Toolkit runs within your local environment or on a hosted virtual machine. Place CFT near the applications, databases, folders, printers, and network resources it needs to reach — on-premises, cloud-hosted, or spread across both.

A smiling IT administrator running Cloud Fax Toolkit across on-premises and cloud-hosted environments

On-premises

Deploy CFT inside your network to connect directly with local folders, SQL databases, printers, MFPs, applications, and identity infrastructure.

Cloud-hosted

Run CFT on a private or hosted virtual machine to support cloud-based systems, distributed locations, and hybrid environments.

Hybrid environments

Connect cloud and on-premises workflows through one configurable fax integration layer.

EHR & Application Integration

Connect the Systems That Already Create and Receive Fax Documents.

CFT lets EHRs and business applications exchange fax documents with WestFax through the integration method that fits their existing workflow. It doesn't force every application into one method — WestFax maps the implementation to how your system already creates, receives, and tracks documents.

Drop-folder processing reads your EHR's own files

CFT parses the structured job files and metadata your systems already produce — including FCL files from Epic and CTL files from PeopleSoft — submits the fax, and writes result files back to update send status, such as NT1 files that post results into Epic automatically.

FCL — Epic CTL — PeopleSoft .FAX files Email (.eml) Structured control files Document & metadata pairs PDF & TIFF

High Availability & Disaster Recovery

Built for Critical Enterprise Fax Workflows.

Deploy multiple Cloud Fax Toolkit instances to support redundancy, business continuity, and disaster-recovery requirements — designed around how your organization runs.

Multiple CFT instancesRun more than one CFT deployment to reduce dependency on a single processing server.
Resilient workflow designDistribute fax processing across environments, facilities, or infrastructure based on your organization's requirements.
Enterprise SQL supportUse appropriate enterprise database architecture where workflow availability requires it.
Disaster-recovery planningDesign CFT as part of your broader continuity and recovery strategy.

Multi-instance, SQL-backed architectures are designed with your team to fit your continuity goals. Specific redundancy and recovery behavior is scoped per deployment.

A focused professional monitoring critical fax workflows on a computer at a standing desk in a bright modern office

Implementation & Support

Your Deployment, Your Pace. Experts on Call.

CFT is built so your team can configure it directly — and our implementation specialists are here the moment you want a hand. They’ve worked these fax workflows across the most demanding environments, they respond fast, and they help you find the approach that fits. You stay in control of what you run and how.

Cloud Fax Toolkit is available to enterprise WestFax accounts. Tell us about your environment and we’ll help you find the right fit.

  • Find the right approachThere’s more than one way to reach your result. We help you weigh the options and choose what fits — the decision stays yours.
  • Help, the moment you want itConfigure it yourself, or have a specialist walk through setup with you. Either way, answers are a message away.
  • Responsive through testingValidating paths or chasing an edge case? Our team is informed and quick to respond, so you’re never stuck.
  • A dedicated account managerOne expert who knows your environment and has your back — a real person to reach, on your terms.

Modular Platform

Use Only the Services Your Environment Requires.

CFT is built as a modular platform. Each deployment is configured around the systems, devices, workflows, and integration methods your organization actually uses — nothing more.

Potential modules Every module is available — switch on only what you need. (Try it.)

CFT can power a single focused workflow or serve as the integration layer for an enterprise-wide fax environment — without introducing unnecessary features or process changes.

From Existing Workflow to Production

Six steps. No surprises.
Live when you’re ready.

You decide what to preserve and how fast to move. We’re alongside whenever you want us.

Map your migration

Map your environment

You inventory the applications, fax lines, folders, databases, printers, and identity systems your faxing touches today — and we help you spot anything easy to miss.

Design routing & rules

You decide how each inbound and outbound job is processed, mapped, and delivered. We recommend what fits your environment — the design is yours to approve.

Deploy CFT

Stand up CFT in the environment that suits you — on-premises, cloud-hosted, or both — with access to the resources it needs to reach.

Connect & validate

Wire up each workflow and test every inbound and outbound path end to end. Nothing goes live until your team has signed off.

Migrate in phases

Move lines and processes over in stages, so nothing breaks and your team is never overwhelmed. You set the pace.

Retire legacy infrastructure

Once your workflows run on WestFax, take the old fax server, boards, and analog lines out of service — on your schedule.

Technical Requirements

What CFT Needs to Run.

Cloud Fax Toolkit installs as a lightweight Windows service on hardware you already have — on-premises or on a hosted VM. It reaches WestFax over a single outbound HTTPS connection, so it drops cleanly into your existing network and firewall policy.

Platform
Windows service — on-premises or hosted VM
Operating system
Windows Server 2012, 2012 R2, 2016, 2019, or 2022
Framework
.NET Framework 4.8
Processor
1.6 GHz minimum · 3.6 GHz recommended (x86 or x64)
Memory
2 GB minimum · 8 GB recommended
Storage
1 GB minimum · 20 GB+ when retaining fax files locally
Database
Bundled SQLite, or Microsoft SQL Server (local or enterprise) for high availability
Service account
Local administrator with “log on as a service” rights
Connectivity
Outbound HTTPS on port 443 — firewall-controllable, no inbound ports to open

Documentation & setup guides

Cloud Fax Toolkit and its guides are available to Enterprise WestFax accounts — tell us about your environment and we’ll get you the installer and the right guide.

Request CFT Access & Guides
  • Administrator GuideReference
  • Quick Start: InstallationQuick start
  • Quick Start: Inbound AutoPrintQuick start
  • Quick Start: Inbound File DownloadQuick start
  • Microsoft SQL Server best practicesReference

FAQ

Frequently asked questions

CFT is a modular, Windows-based integration and routing service that connects WestFax to the systems and workflows inside your organization. It processes inbound and outbound fax documents, connects drop folders and printers, synchronizes users, proxies MFP workflows, and returns fax results to the downstream systems your team already uses.

Moving fax transport to the cloud doesn’t automatically connect every EHR, printer, MFP, folder, directory, and legacy application that still depends on fax. CFT is the local or cloud-hosted execution layer that keeps those workflows connected to WestFax — so migration doesn’t force you to rebuild everything at once.

Yes. CFT can preserve many of the integration patterns that previously ran through a fax server — drop folders, AutoPrint, MFP workflows, directory synchronization, inbound file delivery, and result processing — so you can retire the hardware without rebuilding every workflow. CFT itself is a lightweight service that runs on Windows infrastructure; the exact migration design is scoped around your environment.

Generally no. CFT connects to applications, printers, and folder workflows through the methods they already use, so day-to-day work stays familiar while the fax infrastructure underneath moves to the cloud. WestFax maps the implementation to how your systems already create, receive, and track fax documents.

CFT can support many EHR and enterprise-application workflows through control files, watched folders, PDF or TIFF delivery, metadata files, SMTP, result files, API callbacks, and custom post-processing. It doesn’t force every application into one method — WestFax scopes the right approach during integration mapping.

Ready to scope your fax environment?

Tell us the systems, devices, and workflows that still depend on fax today. We’ll map the right CFT modules and plan your migration.

CFT and related WestFax connector workflows can bridge most major MFP makes and models to WestFax through email, file, server fax kit, or user-aware connector methods — without a brand-specific native app on every device. This is especially useful for older devices that can’t support modern secure connections on their own. Compatibility and configuration are confirmed during implementation.

Yes. CFT can map Active Directory security groups to WestFax users, fax-line access, permission levels, and Email-to-Fax Allowed Senders. Adding or removing someone from a directory group updates their WestFax access on synchronization. SSO authentication is configured separately with WestFax using SAML 2.0.

CFT runs on supported Windows infrastructure that can reach the resources it needs — local Active Directory, file shares, printers, SMTP, databases, and applications. That can be an on-premises server or a customer-managed cloud-hosted server, with additional hosted connector options for certain workflows. The final model is selected during implementation.

CFT supports Microsoft SQL Server and multiple processing instances for high-availability and disaster-recovery architectures. Availability depends on the complete design — database, server, network, and operational controls — which our team scopes alongside yours.