Outbox

The Outbox is a read-only monitoring interface that displays entity change events processed by the LMI automation system. When data changes in LMI (orders, tasks, customers, etc.), the system captures these events and attempts to deliver them to matching automation workflows via webhooks. The Outbox provides visibility into this process, showing which events occurred, which workflows were triggered, and the processing outcome.

Overview

The Outbox module allows you to:

• View a history of entity change events captured by the automation system
• Monitor which automation workflows (subscriptions) were triggered for each event
• Check the processing status of each event (Pending, Success, Failed)
• Navigate directly to external workflow configurations for debugging
• Filter events by entity type, action, or status to focus your investigation

Note

The Outbox is a diagnostic and monitoring tool. You cannot create, edit, or delete outbox events — the data is system-generated and automatically managed.

Accessing the Outbox

Navigate to Settings → Data Management → Outbox from the sidebar menu.

Note

Access to the Outbox requires the Subscriptions permission. Contact your administrator if you don’t see this option in the menu.

Outbox Event List

The main view displays all processed entity change events in a sortable, paginated table.

Table Columns

Column	Description
Entity Type	The type of data that changed (Order, Task, Customer, Location, Product, Tank).
Action	The operation that occurred: Created, Updated, or Deleted.
Triggers	The subscription(s) that matched this event. Click to navigate to the workflow in your automation platform.
Status	The processing outcome: Pending, Success, or Failed. May include a link to execution details.
Created	When the entity change was captured by the system.
Processed	When the automation system processed the event and delivered webhooks.

Sorting

Click any column header to sort the list by that column. Click again to reverse the sort order. By default, events are sorted by Created date (newest first).

Filtering Events

Use the filter bar to narrow down the events displayed. You can combine multiple filters to focus on specific scenarios.

Available Filters

Filter	Options	Use Case
Entity Type	Order, Task, Customer, Location, Product, Tank	Focus on changes to a specific type of data
Action	Created, Updated, Deleted	Find events for a specific operation type
Status	Pending, Success, Failed	Identify failed deliveries or pending callbacks

Filter Examples

• Troubleshoot order automation: Filter by Entity Type = “Order” to see all order-related events
• Find failed deliveries: Filter by Status = “Failed” to identify events that didn’t process successfully
• Check new record automation: Filter by Action = “Created” to see events for newly created entities

Understanding Event Status

Each outbox event has a status that indicates the processing outcome.

Status	Meaning
Pending	The event matched at least one subscription and webhooks were delivered, but the external system hasn’t confirmed completion yet. This is normal for workflows that take time to execute.
Success	The external workflow processed the event successfully and sent a confirmation callback.
Failed	The webhook delivery failed or the external workflow reported an error. Click the status to view execution details if available.
— (empty)	The event is new and hasn’t been processed yet, or no status was recorded.

Tip

Events that match no subscriptions are automatically deleted and won’t appear in the Outbox. If you expected an event to appear but don’t see it, check your Subscriptions configuration.

Navigating to External Workflows

The Outbox provides direct links to your automation platform for quick debugging.

Triggers Column

When an event matches one or more subscriptions, the Triggers column shows:

• Single trigger: Displays the subscription name as a clickable link. Click to open the workflow editor in your automation platform (e.g., n8n).
• Multiple triggers: Displays a badge showing the count (e.g., “3 triggers”). Click to see a popover listing all triggered subscriptions with links to each workflow.

Status Column Links

When the external workflow provides execution details, the Status column becomes clickable. Click to view the specific execution in your automation platform, which is helpful for debugging failed or unexpected workflow behavior.

Relationships & Dependencies

The Outbox is part of the LMI automation infrastructure and works together with several related features.

┌─────────────────────────────────────────────────────────────────┐
│                     Entity Changes in LMI                        │
│              (Orders, Tasks, Customers, etc.)                    │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ captured by database triggers
┌─────────────────────────────────────────────────────────────────┐
│                          OUTBOX                                  │
│           (Read-only monitoring of automation events)            │
│                                                                  │
│  Shows: Entity Type, Action, Status, Triggers, Timestamps        │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ matched against
┌─────────────────────────────────────────────────────────────────┐
│                       Subscriptions                              │
│              (Define which events trigger webhooks)              │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ delivered to
┌─────────────────────────────────────────────────────────────────┐
│                      External Systems                            │
│                (n8n, Make, Zapier, custom APIs)                  │
└─────────────────────────────────────────────────────────────────┘

Related Features

Feature	Relationship to Outbox
Subscriptions	Define which entity changes trigger automation workflows. If an event doesn’t appear in the Outbox, check that a subscription exists for that entity type and action.
External Systems	Configure the automation platforms (n8n, Make, etc.) that receive webhook notifications. The Outbox links to workflows hosted on these systems.
Webhooks	Configure webhook endpoints for event notifications. Related to how events are delivered to external systems.

Best Practices

1. Use the Outbox for troubleshooting, not monitoring — The Outbox is designed for investigating specific issues, not continuous monitoring. For ongoing automation health checks, use your automation platform’s built-in monitoring tools.

2. Start with Status = Failed when troubleshooting — This filter quickly surfaces events that need attention without wading through successful deliveries.

3. Check Subscriptions when events are missing — If an expected event doesn’t appear in the Outbox, the most likely cause is a missing or misconfigured subscription. Events with no matching subscriptions are automatically deleted.

4. Use the workflow links for debugging — Click through to your automation platform to see execution logs, error messages, and workflow state. The Outbox shows what happened; the external platform shows why.

5. Filter by Entity Type when investigating specific workflows — Most automation workflows target a specific entity type. Filtering helps you focus on relevant events.

Troubleshooting

Event not appearing in Outbox

Possible Cause	Solution
No matching subscription	Navigate to Subscriptions and verify a subscription exists for the entity type and action you expect.
Subscription filter not matching	Check the subscription’s filter configuration. The event may have occurred but didn’t match the filter criteria.
Event was cleaned up	Old events are periodically removed. If the event occurred long ago, it may no longer be available.

Status stuck on Pending

Possible Cause	Solution
Workflow still executing	Some workflows take time to complete. Wait for the external workflow to finish and send a callback.
Callback not configured	Verify the external workflow is configured to send a completion callback to LMI.
Callback failed	Check the external workflow’s execution logs for errors when sending the callback.

Status shows Failed

Possible Cause	Solution
Webhook delivery failed	The external system may be unreachable. Check that the webhook URL is correct and the system is online.
Workflow execution error	Click the status link to view execution details in your automation platform. Check the workflow logs for error messages.
Authentication failure	Verify the credentials configured in External Systems are valid and not expired.

Triggers column is empty

Possible Cause	Solution
Event hasn’t been processed yet	Wait for the background processor to match the event against subscriptions.
No subscriptions matched	Check Subscriptions to verify matching subscriptions exist.
Subscription was deleted	If a subscription was deleted after the event was captured, the trigger information may not be available.

Cannot access workflow links

Possible Cause	Solution
External System not configured	Verify the automation platform is registered in External Systems with the correct API URL.
Workflow ID missing	The subscription may not have a valid workflow ID configured. Check the subscription configuration.
Permission denied	You may not have access to the external automation platform. Contact your administrator.