Workday
Workday integrations can deliver payroll, benefits, and other exports to Files.com over SFTP, or retrieve files staged for a Workday import. Files.com supplies the exchange endpoint and the controls around delivery: access for each integration, file-level encryption, routing to vendors, and records of what moved. Workday owns the report, export layout, and business process that consumes an inbound file.
An Enterprise Interface Builder (EIB) integration can use an external SFTP endpoint in either direction. Workday Studio and configured connector integrations can also participate in file exchange. Select the transport supported by the specific integration; Workday's integration concepts explain the different tools. A report exposed through Reports-as-a-Service (RaaS) is a web service that an integration can use as its source, rather than an SFTP delivery by itself.
SFTP Endpoint and Access
Create a dedicated machine account for the Workday integration and enable its SFTP access. Give an outbound Workday feed upload access to its destination folder. An inbound Workday integration needs listing and download access to its pickup folder; grant deletion only if that integration removes collected files.
Use these Files.com values when configuring the Workday transport:
| Connection detail | Files.com value |
|---|---|
| Host | Your site's [subdomain].files.com hostname, or its configured custom domain. |
| Port | 22, or the alternative port in the SFTP connection settings. |
| User | The integration's Files.com username. |
| Authentication | The account's configured password or SSH key method. Install Workday's SSH public key on that user when using key authentication; the matching private key stays in Workday. |
| Directory | The path visible to that user over SFTP. A configured client root folder changes how the path appears. |
| Server identity | The appropriate Files.com SFTP host key for the hostname. This is separate from the user's authentication key. |
For example, if Workday/payroll is presented as the account's SFTP root, Workday delivers to / within that account. Entering /Workday/payroll as well would ask for an additional nested path.
Workday can refer to an SSH authentication key pair through its X.509 key-management tasks. The value registered in Files.com is the SSH public key in a supported format. Keep that authentication key separate from the PGP keys used to protect file contents.
Payroll and Benefits Deliveries
A Workday export can arrive in an intake folder and then be delivered to several recipients. Give each processor or carrier its own destination and access, rather than granting every recipient access to the original payroll folder. An Automation can copy or route the required files, while an SFTP Remote Server provides the connection when Files.com delivers to the recipient's server.
For encrypted exports from Workday, provide Workday with the public PGP key whose private key is held in the Files.com GPG Key Manager. Apply decryption to the receiving folder. For delivery to a processor, encrypt with that processor's public key. These may be different key pairs even when the same file passes through both stages.
Use a separate ready-for-pickup folder for inbound Workday files. Place files there after any required decryption or transformation finishes, so Workday's next retrieval sees the contents its import expects.
Scheduled Runs and Results
Test with the integration's own account and a file matching the intended layout. Confirm the Workday run, the file at the expected Files.com path, and any onward delivery. For an inbound import, also inspect Workday's processing result; a successful SFTP download establishes collection, not acceptance of the records.
An Expectation can detect an export that does not arrive within its required window. Place the expectation at the stage it should measure: arrival from Workday and readiness for a processor are different milestones. Use SFTP Logs for connection failures and the corresponding Automation or Sync records for onward movement.