---
schema_version: "1"
id: ee14b56d02ec4634d8958eb19f2ac34187e8bfd6c950b37b5a2ac17e0d3f7917
title: Automate Processes in Automation Studio
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_as_defining_an_automation.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_as_defining_an_automation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dd33a7977b6c71b5aac684c79a6bc5235633eac31ffb87ebd6636db7c1a751f9
description: Use an automation to start a process when specific criteria are met. For example, when a file is uploaded to the Enhanced SFTP, you can automatically run activities, like an import, a file transfer, or an email send.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Automate Processes in Automation Studio

Use an automation to start a process when specific criteria are met. For example, when a file is uploaded to the Enhanced SFTP, you can automatically run activities, like an import, a file transfer, or an email send.

To build an automation, you choose a starting source, which determines how the automation starts. Then you add the activities that occur when the automation runs. These activities can run sequentially or simultaneously.

When deciding whether to run activities sequentially or simultaneously, consider whether any steps are dependent on each other. If dependencies exist, those steps should be executed sequentially to ensure proper order and avoid errors. Running dependent steps simultaneously can lead to unexpected behavior or incorrect results.

You can choose from these starting sources.

- The schedule starting source starts an automation at specific intervals.
- The file drop starting source starts an automation when a file is uploaded to the Enhanced FTP.
- The trigger starting source starts an automation when a file is uploaded to an external location, such as AWS, Azure, or Google Cloud, and a Trigger API request fires.

For more information, review these topics.

- **[Automation Starting Sources](https://help.salesforce.com/s/articleView?id=mktg.mc_as_triggered_automations.htm&release=264.0.0&type=5)**  
    A starting source defines how an automation starts. You can schedule an automation to run at specific intervals or start an automation when a file is uploaded to the Enhanced FTP. Or, use a trigger to start an automation when a file is uploaded to an external location such as Amazon Web Services, Google Cloud Platform, or Microsoft Azure.
- **[Advanced Run Once](https://help.salesforce.com/s/articleView?id=mktg.mc_as_advanced_run_once.htm&release=264.0.0&type=5)**  
    Automation Studio includes options to schedule an automation, run it automatically when a file is dropped, or run an automation once. Use Advanced Run Once to run only a portion of an automation.
- **[Run a Subset of Activities](https://help.salesforce.com/s/articleView?id=mktg.mc_as_run_a_subset_of_activities.htm&release=264.0.0&type=5)**  
    To run specific automation activities in Automation Studio, click **Run Once** and then select the activities to run.

#### See Also

- [Define the Automation](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_define_automation.htm&release=264.0.0&type=5 "Define a Marketing Cloud Engagement automation using the Fire Event activity to fire an event prompting Journey Builder to detect updates. When you set up the Fire Event activity, select the same data extension used in the entry event you set up in your journey. Automations used for journeys can be set up in advance using Scheduled or File Drop Automations.")