Download files
Retrieve files from remote SFTP paths for parsing, storage, or downstream workflows.
SFTP component
Use SFTP when a customer or partner still exchanges files through secure file transfer.
Download, list, and upload files on an SFTP server as part of automated handoffs.
What this component unlocks
The docs describe SFTP as supporting download, list files, and upload operations. Builders choose an SFTP credential stored in the CXFabric tenant, with an adjacent menu for adding, editing, viewing, deleting, or managing credentials. Download requires a file path with file name, list files requires a directory path, and upload requires selected file content plus a destination path including the filename.
Retrieve files from remote SFTP paths for parsing, storage, or downstream workflows.
Inspect a directory before deciding which files should be processed.
Send generated files or transformed output to an SFTP destination.
Use cases
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use SFTP as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Configuration surface
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Confirm credentials, paths, and filenames before execution.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Handle duplicate files deliberately.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Log transfer status and errors.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Start with an event, use SFTP, then route the result to CRM, ticketing, or a customer-owned system.
Add validation, human approval, and logging around the component before downstream actions execute.
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.