Subscriptions

Subscriptions are webhook registrations created by external automation platforms (primarily n8n) that define which LMI entity changes should trigger webhook notifications. When data changes in LMI—such as tasks, orders, or customers—the system matches those changes against subscription configurations and delivers webhook payloads to the registered URLs.

Overview

The Subscriptions module allows you to:

• View all active webhook subscriptions registered for your organization
• Understand which entity types and actions trigger each automation workflow
• Navigate directly to external workflow configurations in n8n for debugging
• Copy webhook URLs for reference or sharing with team members
• View subscription filters to understand which specific events trigger each workflow

Note

Subscriptions are read-only in the LMI interface. They are created and managed automatically when you activate n8n workflows that include LMI trigger nodes. You cannot create, edit, or delete subscriptions directly from this screen—manage them through your n8n workflow configurations instead.

Accessing Subscriptions

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

Note

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

Subscriptions List

The main view displays all webhook subscriptions registered for your organization in a sortable table.

Table Columns

Column	Description
Workflow Name	The name of the n8n workflow. Click to open the subscription details panel.
Resource	The entity type being monitored (Task, Order, Customer, Location, Product, Tank). Displayed as a badge.
Actions	The operations that trigger the webhook: Created, Updated, or Deleted. Multiple actions are shown as separate badges.
Workflow	A link to the n8n workflow editor. Click to open the workflow configuration in a new tab.

Sorting

Click any column header to sort the list by that column. Click again to reverse the sort order.

Searching

Use the search field in the header to filter subscriptions by workflow name.

Viewing Subscription Details

Click on a workflow name to open a slide-out panel with complete subscription details.

The details panel displays:

• Resource — The entity type being monitored
• Actions — All operations that trigger this subscription
• Workflow ID — The n8n workflow identifier (links to workflow editor)
• Node ID — The n8n trigger node identifier
• Webhook URL — The endpoint where LMI sends event payloads
• Filter — Optional conditions that narrow which events trigger the workflow (displayed as JSON)
• Created At — When the subscription was first registered
• Updated At — When the subscription was last modified

Understanding Subscription Fields

Each subscription defines a specific webhook configuration that connects LMI events to an external workflow.

Field	Description	Example
Workflow Name	Display name from n8n identifying the automation workflow	”Task Assignment Notification”
Resource	The LMI entity type being monitored for changes	Task, Order, Customer, Location
Actions	Which database operations trigger the webhook	Created, Updated, Deleted
Workflow ID	Unique identifier of the n8n workflow	”n8n_workflow_abc123”
Node ID	Identifier of the LMI trigger node within the workflow	”LMI_Trigger_1”
Webhook URL	The endpoint URL where LMI delivers event payloads	”https://n8n.example.com/webhook/…”
Filter	Optional JSON object defining conditions that must match	{"workflow_id": "engineering"}

How Subscriptions Match Events

When an entity changes in LMI, the automation system:

1. Identifies the entity type (resource) and operation (action)
2. Finds all subscriptions matching that resource and action for your company
3. Evaluates each subscription’s filter against the event data
4. Delivers the event payload to all matching subscription webhook URLs

Understanding Filters

Filters allow subscriptions to receive only specific events. Common filter patterns include:

Filter Type	Example	Triggers When
Workflow filter	{"workflow_id": "support"}	Event is for a task in the “support” workflow
Field change filter	{"updated_fields": ["assignee_id"]}	The assignee field was modified
Status filter	{"after.status_id": "completed"}	Status was changed TO “completed”

Tip

If a subscription isn’t triggering as expected, check the filter configuration. The filter conditions must match the event data exactly.

Copying Webhook URLs

To copy a subscription’s webhook URL:

1. Click the workflow name to open the details panel
2. Find the Webhook URL field
3. Click the URL button to copy it to your clipboard
4. A confirmation toast will appear when the URL is copied successfully

This is useful for:

• Sharing webhook endpoints with team members
• Verifying the correct endpoint in your n8n configuration
• Debugging webhook delivery issues

Navigating to External Workflows

Subscriptions provide direct links to your n8n workflow editor for quick access.

From the List View

The Workflow column displays a clickable link. Click to open the n8n workflow editor in a new browser tab.

From the Details Panel

The Workflow ID field is a clickable link when a valid workflow URL can be constructed. Click to navigate directly to the workflow configuration.

Note

Workflow links require your n8n instance to be accessible from your browser. If the link doesn’t work, verify that you have network access to your n8n installation.

Relationships & Dependencies

Subscriptions are part of the LMI automation infrastructure and work together with several related features.

┌─────────────────────────────────────────────────────────────────┐
│                 n8n Workflow with LMI Trigger                   │
│           (Activating the workflow registers the subscription)  │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ creates/updates via API
┌─────────────────────────────────────────────────────────────────┐
│                        SUBSCRIPTIONS                            │
│            (Webhook registrations stored in LMI)                │
│                                                                 │
│  Defines: Resource, Actions, Filter, Webhook URL                │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ matched against by
┌─────────────────────────────────────────────────────────────────┐
│                     Entity Changes in LMI                       │
│              (Orders, Tasks, Customers, etc.)                   │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ logged in
┌─────────────────────────────────────────────────────────────────┐
│                           Outbox                                │
│           (Shows events and which subscriptions triggered)      │
└─────────────────────────────────────────────────────────────────┘
                              │
                              ▼ delivered to
┌─────────────────────────────────────────────────────────────────┐
│                      External Systems                           │
│                (n8n, Make, Zapier, custom APIs)                 │
└─────────────────────────────────────────────────────────────────┘

Related Features

Feature	Relationship to Subscriptions
Outbox	Displays events processed against subscriptions. Use the Outbox to verify that events are being captured and matched to your subscriptions.
External Systems	Defines the automation platforms (n8n, Make, etc.) that host your workflows. Subscriptions link to workflows running on these systems.
Adapters	Related automation connectors for bi-directional integration. While subscriptions handle outbound event notifications, adapters can also receive inbound requests.

Best Practices

1. Use the Outbox for troubleshooting — If events aren’t triggering your workflow, check the Outbox first. It shows which events were captured and whether they matched any subscriptions.

2. Keep filter conditions simple — Complex filters with many conditions are harder to debug. Start with broad filters and narrow them as needed.

3. Name your n8n workflows descriptively — The workflow name appears in the Subscriptions list. Clear names like “Task Assignment Email” are easier to identify than “Workflow 1”.

4. Monitor subscription counts — If you expect automation for a resource type but see no matching subscriptions, verify your n8n workflow is activated and connected to the correct LMI instance.

5. Use workflow links for debugging — When a subscription isn’t behaving as expected, click through to the n8n workflow to check the trigger node configuration and execution logs.

Troubleshooting

Subscription not appearing in the list

Possible Cause	Solution
n8n workflow not activated	Activate the workflow in n8n. Subscriptions are created when workflows are turned on.
n8n not connected to LMI	Verify the LMI trigger node has valid API credentials and can reach your LMI instance.
Different company/environment	Ensure you’re viewing subscriptions for the same company the n8n workflow is configured for.

Events not triggering the subscription

Possible Cause	Solution
Resource/action mismatch	Verify the subscription’s Resource and Actions match the entity type and operation you’re testing.
Filter not matching	Check the subscription’s Filter in the details panel. The conditions must match the event data exactly.
Subscription was deactivated	If you deactivated the n8n workflow, the subscription may have been removed. Reactivate the workflow.

Workflow link not working

Possible Cause	Solution
n8n not accessible	Verify you have network access to your n8n installation from your browser.
Workflow was deleted	The workflow may have been deleted in n8n, but the subscription wasn’t cleaned up.
Invalid webhook URL	The webhook URL format may not match the expected n8n pattern. Check the n8n configuration.

Cannot copy webhook URL

Possible Cause	Solution
Clipboard not available	Some browsers restrict clipboard access. Try using HTTPS or a different browser.
URL is empty	The subscription may be missing webhook URL data. Check the n8n trigger configuration.

Subscription shows outdated data

Possible Cause	Solution
n8n workflow was modified	Update the n8n workflow and save it. Changes should sync to LMI automatically.
Cache issue	Refresh the Subscriptions page to load the latest data.
API sync delay	Wait a few moments and refresh. Subscription updates from n8n may take a few seconds to appear.