SiteTrax Trigger

The SiteTrax Trigger starts a workflow when SiteTrax reports an event — for example, when it reads and identifies a container at a gate or yard. SiteTrax captures container numbers (with image, GPS, and timestamp) and pushes each result to Splice, where this trigger turns it into a workflow execution. Use it to feed yard activity, gate moves, and container reads directly into automation as they happen.

Overview

Use the SiteTrax Trigger when you need to:

• React to container reads in real time - Kick off a workflow the moment SiteTrax identifies a container
• Capture gate and yard activity - Record arrivals, departures, and moves with their GPS and image references
• Bridge SiteTrax into your systems - Push reads into a TMS/WMS, validate against expected containers, or raise exceptions

Endpoint & Setup

The SiteTrax Trigger is delivered over the same HTTP ingress as the Webhook trigger. SiteTrax posts events to the workflow's public endpoint:

POST https://<your-splice-api-domain>/hook/{workflowId}

Configure your SiteTrax account to send events to this URL (copy it from the workflow), then select which events should start the workflow with the Action setting below. The node does not define its own credential — secure the integration at the SiteTrax side and validate the payload inside the workflow. See SiteTrax's API output JSON reference for the authoritative event payload format.

Configuration

Action (required)

The set of SiteTrax events that may start the workflow. Select one or more; only the selected event types trigger a run.

Event	Value	Fires when
Container Read	read	SiteTrax identifies a new container

Output

The trigger emits a single output keyed by the node's name. A Container Read event produces a payload of the form:

{
  "SiteTrax Trigger": {
    "slno": 1,
    "Type": "container",
    "Text": "TLLU2518783",
    "datetime": "2021-11-15T15:28:03.900000Z",
    "datetime_original": "2021-11-15T15:28:03.000000Z",
    "datetime_digitized": "2021-11-15T15:28:03.000000Z",
    "gps_lat": 36.8647946,
    "gps_lon": -76.2262235,
    "Status": "Success",
    "Status_Code": "A0",
    "Asset Image": "https://example.com/img.jpg",
    "Asset Heading": "L2R"
  }
}

Key fields:

• Text - The identified container number.
• Type - The kind of asset read (e.g. container).
• datetime / datetime_original / datetime_digitized - When the read occurred and when the source image was captured/digitized.
• gps_lat / gps_lon - Where the read happened.
• Status / Status_Code - The outcome of the read (e.g. Success / A0).
• Asset Image - URL of the captured image.
• Asset Heading - Direction of travel for the read (e.g. L2R).

Example Usage & Common Use Cases

Validate a Read Against Expected Containers

[SiteTrax Trigger] → [HTTP Request: look up container in TMS]
                        → [If: found] → [Mark arrived]
                                     ↘ [Send Email: unexpected container]

Log Yard Activity

[SiteTrax Trigger] → [Set: shape activity record] → [HTTP Request: append to yard log]

Capture Read Images

[SiteTrax Trigger] → [HTTP Request: download {{Asset Image}}] → [store / attach to record]

How It Works

1. SiteTrax posts an event - SiteTrax sends a POST to the workflow's /hook/{workflowId} URL when a configured event occurs.
2. Match the trigger - The webhook ingress resolves the workflow and selects its trigger node.
3. Filter by action - Only events whose type is enabled in Action start the workflow.
4. Enqueue - The event body becomes the trigger output and a workflow execution is started.

Best Practices

• Select only the events you handle - Enabling just Container Read keeps the workflow from running on event types it isn't built for.
• Validate the payload - Treat the read as untrusted input; check Status / Status_Code and the container format before acting on it.
• Handle failed reads - Not every read is clean. Branch on Status so low-confidence or failed reads are routed to review rather than acted on automatically.
• Make downstream actions idempotent - The same container may be read more than once; key downstream updates on container number + time window so repeats are safe.

Troubleshooting

Common Issues

• No workflow runs on a SiteTrax event - Confirm SiteTrax is posting to the correct /hook/{workflowId} URL, the workflow is active, and the event type is enabled under Action.
• Workflow runs but data is missing - Inspect the captured trigger output; SiteTrax payload fields vary by read, so guard against absent fields downstream.

Debugging Tips

• Inspect the captured sample - The trigger output is stored as node sample data on each run; use it to design downstream nodes.
• Test with a manual POST - Send a sample Container Read body to the URL with curl to confirm the endpoint and downstream logic before relying on live reads.

Related

• Webhook - The general-purpose HTTP trigger this node is built on
• SiteTrax API output JSON - SiteTrax's authoritative reference for the event payload this node receives
• Trigger Nodes - Overview of all available workflow trigger types