How to Configure the File Transfer Activity in Adobe Campaign Classic

Adobe Campaign Classic’s File transfer activity is a workflow activity for retrieving a file for downstream processing or sending a workflow-generated file to another location. Configure it by selecting the required transfer action, completing the connection and file-location fields shown for that action, and then placing it at the correct point in the workflow. The File transfer activity configuration options determine the fields available for the selected action.

The File transfer activity enables you to send or receive files, check whether a file exists, and list files stored on a server. It supports Azure Blob Storage, Amazon S3, FTP, and SFTP.

How the File Transfer Activity Fits into a Workflow

File transfer moves a file. Processing the file’s contents and updating Campaign data are separate workflow steps.

A download flow can use this sequence:

File transfer
 |
File-processing activity
 |
Data-processing activity - Data loading

An upload flow places File transfer after the activity that creates the outbound file:

Query or data preparation
 |
File-generation activity
 |
File transfer

The activity runs when the workflow reaches it. Review the workflow’s scheduling and transitions before testing so that the transfer is triggered only after its required input is available. For the workflow-level execution model, see how Adobe Campaign Classic workflows automate connected activities.

Configure the Transfer Action

• Open the workflow and add a File transfer activity.
• Connect it after the activity that should trigger the transfer.
• Open the activity properties.
• Select the action that matches the direction of the transfer.
• Complete the connection, location, and file-selection fields displayed for that action.
• Review any post-transfer file-handling options before saving.
• Connect the outbound transition to the next processing or completion step.

Configure a download when Campaign must retrieve an inbound file. Configure an upload only after an earlier activity has created the file that Campaign must send.

Do not treat download and upload as the complete set of possible actions without checking the activity properties in the relevant Campaign environment. Use the labels and fields displayed by the activity for the action being configured.

Configure an Inbound File Download

For a download, first select the connection or location from which Campaign will retrieve the file. Then provide the remote directory, file name, or selection value required by that transfer method.

Confirm all of these values together before enabling the workflow:

• The selected action is a download action.
• The configured connection points to the intended environment.
• The directory and file name identify the intended inbound file.
• The source system has completed writing the file before the workflow reaches File transfer.
• The downstream activity is configured to use the file made available by the transfer.

For example, an inbound process can retrieve a daily customer file and then pass it to a file-processing step. Reconciliation and field updates belong in later data-processing activities, such as the Update data activity, rather than in File transfer itself.

Configure an Outbound File Upload

For an upload, identify the file produced by the upstream workflow activity, then configure the receiving connection and destination location.

Validate the outbound sequence in this order:

• The upstream activity creates the intended file.
• File transfer selects that exact file.
• The receiving connection and destination identify the correct environment and location.
• The outbound transition runs only after the transfer completes.

A successful file-generation step does not by itself send a file to an external destination. Keep file creation and file transfer as separate, visible workflow steps so that each stage can be checked independently.

Check File Names, Locations, and Timing

Most transfer investigations start with the configured file location and name. Compare the activity configuration with the actual inbound or outbound file, including its extension and character case.

For inbound processing, also confirm the source system’s delivery timing. A workflow that runs before the source file is available cannot retrieve the intended file. For outbound processing, confirm that the file exists before the upload action begins.

Use a small, controlled test file when validating a new connection or destination. Confirm the destination and the downstream workflow behavior before scheduling recurring transfers.

Handle Post-Transfer Files Safely

Do not enable post-transfer deletion, movement, or overwrite behavior until the file owner has confirmed retention and restoration procedures for the source or destination system. A file removed after transfer may be unavailable for investigation or controlled reprocessing.

Where the sending system provides its own archive process, keep completed files outside the active inbound directory to separate them from new inputs. That archive process is an external operational control, not a File transfer capability.

Resolve Common Transfer Failures

No file is retrieved

Recheck the selected action, connection, directory, and file name first. Then confirm that the source system has completed delivery before the workflow runs.

The transfer completes but downstream processing fails

Verify that the downstream activity is using the transferred file and that its file-processing configuration matches the actual file structure. File transfer confirms movement of a file, not the correctness of its contents for later processing.

An upload reaches an unexpected destination

Review the selected connection and destination location. Use distinct names for development, test, and production connections so that the workflow configuration makes the target environment clear.

A file is missing after a transfer

Review the activity’s post-transfer file-handling setting before rerunning the workflow. Confirm retention and restoration procedures before changing that setting or repeating the transfer.

Share With Others