Automation Builder

Learn about how the visual automation builder works

Couchdrop automations are built using a visual builder that requires no code. The builder supports multiple steps through primary actions and sub-actions.

How the builder works

Automations have two main pathways. Moving down the tree are primary actions. Moving to the right are sub-actions.

See the sample image below of an automation created with the visual builder.

It's important to understand Primary Actions and Sub-actions and the processing order to avoid errors.

Primary Actions

Primary actions act on the original file. This means that when there is a Copy action, any sub-actions apply to the copy and do not apply to the original file. Because of this, some actions like "Rename File" are unavailable in Primary actions to avoid errors.

Sub-actions

Sub-actions are branches to the right. These actions act on the modified file if a second file has been created due to a copy or similar action. If there is only one file, Sub-actions act on the original file and function essentially the same as primary actions.

Processing Order

Automations are processed top-to-bottom, left-to-right. This means that sub-actions occur before the next primary action.

If a sub-action fails, then Couchdrop will NOT continue to process any child actions

The builder shows the order that actions will be processed by showing them at different levels, with higher levels processed first.

See the image below for an example of processing order in a multi-step workflow.

Click to enlarge

The automation in the example will then be processed as follows:

1. A file is transferred to a folder called "Compress".

2. The file is compressed with gzip.

3. A copy of the file is transferred to a folder called "Final".

4. The file in "Final" is decompressed with gzip.

5. The decompressed file in "Final" is renamed to "Final Report.xls".

6. The compressed file in "Final" is deleted

7. The compressed file in "Compress" is renamed to "Archive.gzip"

8. The renamed "Archive.gzip" file is moved to a folder called "Archive"

9. A notification email is sent to "[email protected]"

Modifying an automation

Once an action is chosen, the action type cannot be changed directly. Instead, the action must first be deleted and then replaced with a new action.

When deleting an automation action, if the action has sub-actions, those sub-actions will be deleted as well. When this applies, you will receive a warning explaining the number of actions that will be deleted and will need to confirm deletion.