Automations

Automations are visual workflows that respond to ShipOS events. A workflow starts with a trigger, can branch through conditions, and runs one or more actions.

Go to ShipOS → Automations (opens the Cybership dashboard in a new tab).

Create an automation

1. Click Create Automation.
2. Enter an Automation Name.
3. Add an optional description and tags.
4. Click Create Automation to open the builder.

Tags help organize the Automations table. The table also shows whether a workflow is enabled and how many executions it has recorded.

Build the workflow

An automation graph contains:

• Trigger: The event that starts the workflow
• Condition: A comparison or group of comparisons that controls a path
• Action: Work ShipOS performs

Add and connect steps in the visual builder. A publishable workflow needs one configured trigger and at least one configured action. ShipOS also checks for duplicate links, invalid variables, and incomplete step configuration.

Triggers

Choose the event that represents the start of the workflow, such as an order, fulfillment, or other supported ShipOS activity.

The trigger supplies event variables to downstream conditions and actions. If you later change the trigger, review every field that references the previous trigger's data.

Conditions

Conditions compare values from the trigger, runtime context, or earlier step output.

Use groups to combine comparisons with logical rules. Array-aware conditions can evaluate records such as line items without copying the same branch for every item.

Actions

Current action types include:

• Send an email
• Add an order line item
• Set order priority
• Set a carton, service level, or rate shop
• Mark an order as fragile
• Set Incoterm or EEL/PFC
• Require a pack shot
• Enable or disable address verification
• Show or hide unfulfilled items on the packing list
• Show or hide prices on the packing slip
• Enable or disable Tote QA

The action picker shows only actions available to the current workflow and feature configuration.

Configure packing-slip prices

Use Show Prices on Packing Slip to override price visibility for one order.

1. Add the action after an order-capable trigger.
2. Set the Order ID from the trigger or an earlier step.
3. Choose to show prices, hide prices, or leave the value unset to inherit configuration.
4. Save the action.

The inherited default comes from the resolved Configuration for the team, merchant, and order.

Use variables and Liquid

Fields with a + variable picker can use values from:

• The trigger event
• Runtime context
• Earlier action outputs

These fields are rendered with Liquid. Use the picker to insert a valid path, then combine it with text, filters, conditionals, or loops where supported.

See the Liquid templating reference.

Save, publish, and enable

• Save keeps the current builder changes as a draft.
• Save & Publish saves the draft and makes it the published version.
• Enable allows the published workflow to run when its trigger fires.
• Disable stops new executions without deleting the automation.

Publishing does not automatically fix incomplete steps. Resolve every validation issue shown by the builder before publishing.

Review executions

Open an automation and select Executions to review:

• Execution status
• Published version used
• Trigger event
• Start time and duration
• Completed step count
• Step inputs, outputs, and errors

Related-resource links open the ShipOS record associated with an execution when one is available. A failed execution can be rerun when its supported actions allow it.

Related guides

• Liquid Templating
• Configuration
• Fulfillment Orders