Editing Move or Copy actions (section)

= How to Move or Copy Actions in Automations =

== Introduction == 
The '''Move or Copy''' actions feature in ActiveCampaign allows users to efficiently rearrange or duplicate actions within an automation. This feature is particularly beneficial for users who may want to refine their automations without the hassle of deleting and recreating actions. By streamlining action placements, users can enhance their workflow, save time, and ensure that their automations run smoothly and effectively.

== How to Access this Feature == 
To access the Move or Copy actions feature, you need to have an active automation set up in your ActiveCampaign account. Navigate to the desired automation and identify the action you wish to move or copy. This can be achieved by selecting the action within the automation editor.

== Step-by-Step Instructions == 

=== Moving or Copying a Single Action === 
1. Drag and drop the existing action onto the '''+"''' symbol where you’d like to move or copy this action within your automation.
2. You will see a modal titled '''Move or Copy Action''' appear:
   * This modal will give you options to either '''Move single action''' or '''Copy single action'''. 
   * Please note that these options are only accessible if the automation has a single branch.
3. Choose one of the following options:
   * '''Move single action''': This will relocate the selected action to the new specified location.
   * '''Copy single action''': This will duplicate the action in the new location while retaining the original in its initial spot.
4. If your action is a '''Wait''' or '''Jump To''' action, additional choices will appear for handling any contacts currently in that action. Select the best option for your needs.
5. Click '''OK''' to finalize your choice and execute the move or copy action.

=== Moving or Copying Multiple Actions === 
1. If you want to move or copy multiple actions, ensure you first create an open path using an '''If/else''' action. Remember, you cannot move multiple actions into the same path.
2. Drag and drop the first action from the group of actions you wish to move or copy onto the '''+"''' symbol on the open path within your automation.
3. The same '''Move or Copy Action''' modal will appear.
4. You can choose among the following options:
   * '''Move single action''': Moves only the single action to the new path.
   * '''Move this action and all following actions''': Moves the selected action along with all subsequent actions to the new path.
   * '''Copy single action''': Duplicates the single action in the new location.
   * '''Copy this action and all following actions''': Copies the selected action and every action that follows it to the new path.
5. As with single actions, if one of your selected actions is a '''Wait''' or '''Jump To''' action, additional options will appear for reviewing how contacts should be handled.
6. Click '''OK''' to complete the action for multiple items.

== Configuration Options and Settings == 
When utilizing the Move or Copy actions feature, be mindful of the following configuration options:
- '''If/else action''': Necessary for creating an open path when moving multiple actions.
- '''Wait action''': Consider how this may impact any contacts currently in the action. You will need to select an appropriate option based on your automation's needs.
- '''Jump To action''': Similar to the '''Wait action''', any contacts in this action need to be addressed properly when reorganizing.

== Best Practices and Tips == 
- Always review the automation after moving or copying actions to ensure that the flow and logic remain intact.
- Use '''If/else actions''' to structure your automation logically, making future adjustments easier.
- Consider making a copy of your entire automation before making significant changes to preserve the original structure.
- Regularly test your automations after making changes to ensure contacts are being processed as intended.

== Common Use Cases with Examples == 
1. **Refining Automation Flow**: If you notice that a certain action is better placed after another, you can move it quickly without the need for re-creation.
2. **Duplicating Actions for Variations**: Instead of setting up similar actions multiple times, use the copy feature to duplicate existing ones and modify as necessary.
3. **Response Variations**: If running an automation with various response options, use copying to test different follow-up actions without affecting the original.

== Troubleshooting == 
- If you encounter issues moving or copying actions, ensure that your automation is not overly complicated or contains other paths that may restrict the movement.
- Verify that the action types (especially '''Wait''' and '''Jump To''') are compatible with your intended path before moving them.

== Related Features == 
- [[Automations]]
- [[If/else actions]]
- [[Wait actions]]
- [[Jump To actions]]

== FAQ == 
'''Q1: Can I move actions into a path that is already occupied?'''
A1: No, you cannot move multiple actions into the same path. Ensure that you have an open path using an '''If/else action'''.

'''Q2: What happens to contacts in a Wait action when I move it?'''
A2: Additional options will appear for handling contacts currently in the '''Wait action''' when moving it.

'''Q3: Can I copy actions to different automations?'''
A3: No, the Move or Copy actions feature is specific to the automation you are currently working within.

'''Q4: Is there a limit to how many actions I can move or copy at once?'''
A4: There is no explicit limit, but ensure that the configuration remains viable within the context of your automation logic.

'''Q5: What plans include the Move or Copy actions feature?'''
A5: This feature is available on all plans: Starter, Plus, Pro, and Enterprise.

'''Q6: Can I undo a move or copy action?'''
A6: If a move or copy has been completed, it cannot be undone directly. Consider creating backup copies of your automation prior to making changes.

'''Q7: Are there any special requirements for moving actions?'''
A7: Yes, if moving multiple actions, an open path must be created with an '''If/else action.''' Single actions can be moved without such a requirement.

```