Actions Reference
Actions define what happens when a workflow's trigger fires and all filters pass. A workflow must have at least one action before it can be activated. To add an action, click the Filter / Action toggle at the top right of the workflow editor and select an action from the list.
| Action | What it does | Key options and notes |
|---|---|---|
| Add Alert | Adds a specific alert to the shipment. | Select from the available alerts list. |
| Resolve Alert | Resolves (clears) a specific alert on the shipment. | Select from the available alerts list. |
| Add Assignment | Assigns the shipment to a specific LSP staff member or staff type. | Supports an assignment delay. Click the blue pencil icon to assign by staff type instead of an individual. |
| Resolve Assignment | Resolves the assignment for a specific staff member on the shipment. | |
| Resolve All Assignments | Resolves all open assignments on the shipment at once. | Commonly used when a shipment is marked as Delivered. |
| Add Assignment with Message | Creates an activity log and assigns it to a staff member with a custom message. | Supports assignment delay. Use the pencil icon to assign by staff type instead of an individual. |
| Send Email | Sends an automated email when conditions are met. | Choose from standard or up to 20 custom content templates. Configure sender, recipients, CC, subject, and optional attachments. See the email details section below. |
| Update Shipment Status | Automatically changes the shipment to a selected status. | Choose the target status from the dropdown. |
| Carrier Check Call | Sends a check call to the carrier via email or text message. | Email goes to the first dispatcher in the carrier profile. Text goes to the driver's cell phone. Will not trigger while a shipment is in Committed status — only fires from Dispatched status onward. |
| Assign Carrier Check Call Activity | Assigns the activity log from a carrier check call response to a designated staff member. | Use with the Carrier Check Call Response trigger. Click the pencil icon to assign by staff type. |
| Remove Carrier | Removes the assigned carrier from a specific transit leg. | Cannot run if the transit leg's billing status includes records in "No Accounting" or "Created" states. |
| Remove Shipment Reference Number | Removes a specific type of reference number from the shipment. | Useful for data cleanup workflows. |
| Add Carrier | Automatically assigns a carrier to a specific transit leg when workflow conditions are met. | Includes carrier dropdown, transit leg selector, and override toggle. The user in the Working As field is automatically set as Carrier Rep at execution. |
| Add Carrier Label | Applies one or more carrier labels to a shipment based on workflow conditions. | Labels applied here can later be used to filter and segment carriers in Truckload Quoting. |
| Update Buy/Sell Fuel | Sets the fuel amount using a selected calculation type and rate value. | Calculation types: Flat, Cost per Mile, Minimum Charge, Percentage of Linehaul. |
| Send Webhook | Transmits shipment data as a webhook payload to a specified URL. | Payload matches the Shipment Create/Update webhook format. Optional username, password, and license key for authentication. |
Send Email Action Details
Recipients
Select recipients from the available staff type list, or enter email addresses manually by clicking the pencil icon. Separate multiple addresses with commas.
Two special recipient options:
- All Assignee — sends to every staff member currently assigned to the shipment.
- New Assignee — only works with the Assignment Added trigger; sends only to the newly assigned staff member.
Carrier Dispatcher recipient hierarchy
When Carrier Dispatcher is selected as a recipient, the system looks for an email address in this order:
- Carrier Dispatcher in the Shipment Profile — used first if an email is present.
- Favorite Dispatcher in the Carrier Profile — used if no email is found on the shipment.
- First Dispatcher in the Carrier Profile — used as a final fallback.
- No email found — if no dispatcher email exists in either profile, the action will not execute and the workflow will fail.
Attachments
Two attachment types are supported:
- TMS Documents — system-generated documents such as BOLs and Carrier Confirmations. These are always available.
- User Uploaded Attachments — documents manually added by users. If no matching attachment exists when the workflow runs, the action will fail. When multiple attachments of the same type exist, only the most recent one is used.
Note: If a selected content template includes attachment tags, the relevant TMS Documents will be automatically pre-selected in the action form.