Pulse Flows

Automate the operational loops your team runs by hand

Pulse Flows is a visual workflow builder for freight operations. No code. No IT ticket. Triggers, tools, approval gates, and run history — built by the ops team, for the ops team.

Common triggers
Shipment delayed > X days Invoice over threshold Document missing at milestone Carrier performance drop New booking approval Scheduled interval CargoWise webhook
Common Use Cases

The workflows your team runs on email.

Every freight operations team manages a set of recurring approval and notification chains. The same triggers. The same recipients. The same actions. Every day. Pulse Flows handles them automatically.

01

Exception escalation

A shipment exceeds the configured delay threshold. Pulse Flows notifies the operations manager, raises an exception alert, and logs the escalation. No one has to check manually.

02

Invoice approval gating

An invoice arrives above the auto-approve threshold. Pulse Flows routes it to the designated approver. The approver clicks approve or decline. The decision is logged with the approver’s name and timestamp.

03

Document checklist enforcement

A shipment reaches a specific milestone and a required document is missing. Pulse Flows notifies the responsible team member and tracks whether the document was uploaded.

04

Carrier performance alerts

A carrier’s on-time rate drops below a configured target. Pulse Flows notifies the procurement team and creates a carrier performance exception for review at the next contract meeting.

05

Booking confirmation

A new booking is created. Pulse Flows sends the client a confirmation email from your branded domain, attaches the booking document, and updates the order status to confirmed.

06

CargoWise write-backs

A flow step can write a field back to CargoWise via the eAdaptor integration. Status updates, milestone completions, and approval decisions can be reflected in your TMS without manual entry.

The Builder

Built in the platform by the operations team.

No development resources required. Open the flow builder. Select a trigger. Add a tool step. Set the conditions. Save and activate. The whole thing takes minutes, not weeks.

1

Choose a trigger

Select from the trigger catalog: a shipment event, a scheduled time, a threshold breach, or an inbound webhook from CargoWise. The trigger defines when the flow fires.

2

Add tool steps

Chain the tools your workflow needs: send an email, raise an alert, update a status, attach a document, write back to CargoWise. Add as many steps as the workflow requires.

3

Add a gate if needed

Insert a human approval checkpoint before any step. Pulse Flows pauses and routes the decision to the right person. When they decide, the flow continues or stops — and the outcome is logged.

4

Save and activate

Activate the flow. Every execution is logged in run history: what fired, what happened, what was skipped, and where it stopped. Replay any run. Debug from the log.

Human Checkpoints

Automation with a human in the loop.

Some decisions should not be fully automatic. Pulse Flows lets you insert an approval gate at any point in the workflow — before a payment, before a status update, before an escalation.

Gate behavior

When execution reaches the gate, the flow pauses. An approval request is sent to the designated user. When they approve, the flow continues from the next step. When they decline, the flow stops and logs the outcome.

The approver never has to log into a separate tool. Approval works via in-platform notification or email.

Full audit trail

Every gate decision is logged with the approver’s name, timestamp, and outcome. Run history shows the complete execution path, including which gates were reached, who decided, and what happened next.

The audit record is available per flow run and per shipment.

Run History

No black-box automation.

Run history shows every execution — what fired, what happened, what was skipped. If a step fails, the error is visible. Fix it and re-run. Every execution is auditable.

Per-run log

Each execution creates a log entry: trigger event, steps executed, tool outputs, gate decisions, and final status. Accessible from the flow dashboard and from the related shipment or order record.

Step-level visibility

See the exact state at each step in the execution. Which email was sent. Which field was updated. Which approval was pending. No guessing whether the flow actually ran.

Replay

Re-run any failed execution once the underlying issue is corrected. No need to wait for the trigger to fire again. Replay from the run history log in one click.

Common Questions

Pulse Flows specifics.

Does Pulse Flows require technical setup?

No. The flow builder is a visual interface inside the PulseCargo platform. Operations team members with admin-level access can build, activate, and edit flows without engineering involvement.

Can a flow write back to CargoWise?

Yes. The CargoWise write-back tool is available as a step in any flow. Status updates, milestone completions, and custom field updates can be pushed back to your CW environment via the eAdaptor integration.

What happens if a flow step fails?

The failure is logged in run history with the error detail. The flow stops at the failed step. The operations team is notified. Once the underlying issue is corrected, the run can be replayed from the log.

Can I see which flows ran on a specific shipment?

Yes. The run history is linked to the shipment or order record that triggered the flow. From the shipment view, you can see every flow that executed, every step that ran, and every gate decision that was made.

How many email chains is your team running today?

Pulse Flows replaces the manual ones. Contact us to see a live build session.

Request a demo →
Preview Pulse VOX

Tap to speak