Tutorial: Create a simple workflow that transfers a package

Edit online

In this tutorial, you create and configure an automated workflow that triggers each time a package is received by a shared inbox in Aspera on Cloud. While this example may not match your precise use case, it demonstrates the basic process for assembling the components of a workflow in the Automation app.

1. Create the workflow and add the trigger

Edit online

In this procedure, you create a new workflow and then create the trigger. The triggering event for this workflow is a package arriving in a shared inbox in Aspera on Cloud. You also create custom conditions using metadata that is already configured on the shared inbox.

  1. On the Workflows page, click Create new.
  2. Enter a name for your workflow, then click Submit.
  3. Select the trigger for the first step.
    In the New trigger window, click Shared inbox event.
  4. In the View as field, select User or Admin.
  5. Select the workspace where this even must occur to trigger the workflow.
  6. Select the shared inbox. Click Save.
  7. Under Workspace, select the desired workspace.
    Under Name, select a shared inbox. Click Select.
  8. Return to the right pane, under Trigger location.
    To create a metadata condition, select Custom in the right pane.

    From the menu, select Any of the following conditions.

  9. Under Condition 1, select a field, such as File type.
    Select a matching condition, such as Contains.

    In the text box, enter a string, such as jpg, png.

    The transfer now triggers for a package with a metadata field called “File type” that contains the values “jpg” or “png”.
  10. Click Save.

2. Create actions in the workflow

Edit online
In this procedure, you select an action for the second step in the workflow. Each step can contain one or more parallel actions.

You will configure a transfer action, which transfers a file or folder from the shared inbox you selected in the first procedure to the node you select here. You then create a final step to notify stakeholders.

  1. Select an action for the second step in the workflow. Each step can contain one or more parallel actions.
    In the right pane, click Transfer.
  2. Click Source location for your transfer, then click Same as trigger.
  3. Click Destination location for your transfer; then click Nodes.
  4. In the Node access dialog, select a node from the dropdown; then enter the secret.
    Click Log in.
  5. Select a folder from the Name list, then click Select.
  6. To add a final step with a notification action, click the plus sign (+) to the right of the transfer action step.
  7. In the right pane, click Notify.
  8. Enter an email address in the To field, and add an optional message.
    Click Save.
    Now you’re ready to activate your workflow.

3. Activate and launch your workflow

Edit online

In this final procedure, you activate your workflow so that it begins automatically launching a new job (a running instance of the workflow) each time a package is received by the shared inbox.

  1. At the top right of the page, click Activate.
  2. In the Activate workflow dialog, click OK.
    Each new job transfers the package from the shared inbox to the node (transfer server) location that you specified in your workflow configuration.
    Note: The following is the number of jobs that Automation can run at the same time (in parallel), by subscription type:
    • Standard plus edition of Aspera on Cloud: 5 jobs
    • Premium edition of Aspera on Cloud: 10 jobs
    As each running job completes, another job is released from the queue.
  3. To view the status of your workflow, click Job queue in the left pane.