'File Drop' Starting Source in Automation Studio

breakdown on all steps

Create 'File Drop' Starting Source in new automation

Automation Studio -> click 'Overview' tab -> Click 'New Automation' button. -> select drag and drop 'File Drop' on the canvas, then click on 'File Drop' again. -> Click 'Configure', add select 1 of 2 -> 1. Choose whether to use a file name pattern for the trigger: If you’re using a file name pattern, select an operator and provide text for the pattern. Don’t include a file extension. If you select 'Contains', Automation Studio reads all files dropped into the Import or Triggered_Automations directories in the Enhanced SFTP location. 2. If you select No Filename Pattern, assign a directory as a trigger for one automation at a time. You can use the Import or Triggered_Automations directory, or a subdirectory of one of these folders, as the assigned directory. When a dropped file matches more than one active trigger, Automation Studio randomly selects one trigger. Alternatively, to make sure that your trigger is selected, use subdirectories when you select file name pattern matching. -> If you want Automation Studio to ignore new requests that occur when an automation is running, ‘turn off queuing’. Note If you pause or deactivate a File Drop Automation, any queued instances of the automation that have a status of ‘QueuedFile’ retain that status permanently. -> Select the directory for the system to watch. When a file is dropped in this folder, the automation starts. -> click 'Done'. -> Drag an activity onto the canvas. -> To view all activities of the selected type, click 'Choose'. All existing configured activities of that type appear. You can sort the columns or search by ‘keyword’, ‘name’, or ‘external key’. To see a summary, click an activity. -> Select an activity or create one. -> Add and configure more activities as needed. -> Save and activate the automation. -> To receive notifications about automation success or failure, on the Activity tab, select 'Notification Settings' and enter an email address. -> If you edit an active automation or the activities in it, all running instances of the automation are stopped. Future runs of the automation are paused until all activities are defined and saved.

Add ‘File Drop’ starting source

Automation Studio -> click 'Overview' tab -> Click 'New Automation' button. -> select drag and drop 'File Drop' on the canvas, then click on 'File Drop' again. -> Click 'Configure'

File name pattern for the trigger

select an operator and provide text for the pattern. Don’t include a file extension. If you select 'Contains', Automation Studio reads all files dropped into the Import or Triggered_Automations directories in the Enhanced SFTP location.

No Filename Pattern

assign a directory as a trigger for one automation at a time. You can use the Import or Triggered_Automations directory, or a subdirectory of one of these folders, as the assigned directory. When a dropped file matches more than one active trigger, Automation Studio randomly selects one trigger. Alternatively, to make sure that your trigger is selected, use subdirectories when you select file name pattern matching.

‘Turn off queuing’

If you want Automation Studio to ignore new requests that occur when an automation is running, ‘turn off queuing’. Note If you pause or deactivate a File Drop Automation, any queued instances of the automation that have a status of ‘QueuedFile’ retain that status permanently. Select the directory for the system to watch. When a file is dropped in this folder, the automation starts. -> click 'Done'.

'Notification Settings'

To receive notifications about automation success or failure, on the Activity tab, select 'Notification Settings' and enter an email address. -> If you edit an active automation or the activities in it, all running instances of the automation are stopped. Future runs of the automation are paused until all activities are defined and saved.

No - (It is Efficient) place 3rd place use of network bandwidth compare to 1st place ‘API to start an automation (developers API not Automation Studio)’ or 2nd Place ‘Schedule’ starting source. No external network requests are made, and no empty "polling" schedules run. The network and processing resources are only triggered exactly when needed—the moment a file completely finishes uploading. 4th place is Trigger API/Triggered Automation starting source is below it.

Does ‘File Drop’ use most network bandwidth compare to ‘API to start an automation (developers API not Automation Studio)’ , ‘Schedule’ starting source or Trigger API/Triggered Automation starting source?

Import of data

Does ‘File Drop’ starting source works with import of data or export of data?

Yes - monitors Marketing Cloud Enhanced FTP site and directories

Does File Drop starting source monitors specific directories such as /Import/ or custom subfolders on your assigned internal Marketing Cloud Enhanced FTP site?

No - Safehouse is internal secure temporary storage location.

Does File Drop starting source monitors Safehouse?