External Systems

External Systems is a configuration registry where you define connections to third-party platforms such as workflow automation tools (n8n, Make, Zapier), ERP systems, or custom APIs. These registered systems serve as the foundation for adapters, webhooks, and other integration features throughout LMI.

Overview

The External Systems module allows you to:

• Register third-party platforms with their connection details
• Store API URLs and authentication credentials securely
• Provide a centralized registry of all external integrations
• Enable adapters and webhooks to reference configured systems
• Support quick navigation to external workflow configurations

Accessing External Systems

Navigate to Settings → Data Integration → External Systems from the sidebar menu.

Note

Access to External Systems requires appropriate permissions. Contact your administrator if you don’t see this option in the menu.

External Systems List

The main view displays all external systems configured for your organization in a sortable table.

Table Columns

Column	Description
Name	The external system name. Click to open the edit panel.
ABBV	The abbreviation or short code for the system.
Description	A brief description of what this system is used for.

Searching External Systems

Use the search field in the header to filter external systems by name, abbreviation, or description. Results update as you type.

Sorting

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

Adding an External System

1. Click the dropdown menu (three dots) next to the page title
2. Select Add External System
3. Complete the required fields in the form
4. Click Save

External System Fields

Field	Required	Description
External System Name	Yes	A descriptive name for the platform (e.g., “n8n Production”, “Make.com”, “SAP ERP”).
External System Abbreviation	Yes	A short code to identify the system (e.g., “N8N”, “MAKE”, “SAP”). Used in displays where space is limited.
External System Description	Yes	Explains what this system is used for and any relevant context for your team.
External System Username	No	Username for basic authentication, if required by the external system.
External System Password	No	Password for basic authentication, if required by the external system.
API URL	No	The base URL for the external system’s API (e.g., https://n8n.yourcompany.com). Used by adapters to construct navigation links.
API Token	No	An API authentication token or key for the external system.

Tip

The API URL field is particularly important for workflow automation platforms. When configured along with an External ID in adapters, it enables one-click navigation from the adapters list directly to the workflow configuration in the external platform.

Editing an External System

1. Click on the external system name in the list to open the edit panel
2. Modify the desired fields
3. Click Save to apply changes

All fields except the system ID can be modified. Changes take effect immediately after saving.

Caution

Modifying credentials (username, password, or API token) may affect active integrations that rely on this external system. Coordinate with your team before making changes to production systems.

Understanding Credentials & API Configuration

External Systems store two types of authentication credentials:

Basic Authentication

• Username and Password fields
• Used when the external system requires HTTP Basic Auth
• Adapters and webhooks can use these credentials when making API calls

Token-Based Authentication

• API Token field
• Used for Bearer token or API key authentication
• Supports long tokens (the field accepts multi-line input)

API URL Purpose

The API URL serves multiple purposes:

1. Navigation — When combined with External IDs in adapters, enables direct links to external workflows
2. API Calls — Provides the base URL for outbound API requests
3. Documentation — Helps your team identify which environment (dev, staging, production) this system represents

Note

LMI does not validate credentials when saving an external system. Verify your credentials work correctly in the external platform before using them in production integrations.

Relationships

External Systems serve as the foundation for multiple integration features in LMI.

┌─────────────────────────────────────────────────────────────┐
│                     External System                          │
│  (n8n, Make, Zapier, ERP, Custom API)                       │
│                                                              │
│  - Name / Abbreviation                                       │
│  - API URL / API Token                                       │
│  - Username / Password                                       │
└─────────────────────────────────────────────────────────────┘
                           │
                           │ referenced by
                           ▼
┌──────────────────────────────────────────────────────────────┐
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐  │
│  │   Adapter   │  │   Webhook   │  │   Billing Profile   │  │
│  │             │  │             │  │                     │  │
│  │ Automation  │  │   Event     │  │  Third-party        │  │
│  │ connectors  │  │   triggers  │  │  billing systems    │  │
│  └─────────────┘  └─────────────┘  └─────────────────────┘  │
└──────────────────────────────────────────────────────────────┘

Related Features

• Adapters — Automation connectors that send data to external systems when events occur in LMI
• Webhooks — Event notifications that can be linked to external systems
• Subscriptions — Subscribe to specific events for automated processing

How Features Use External Systems

Feature	How It Uses External Systems
Adapters	Selects an external system to associate the automation with. Uses API URL + External ID to create clickable links to external workflows.
Webhooks	Can optionally link to an external system for organization.
Billing Profiles	References external systems for third-party billing integration.

Best Practices

1. Use clear, consistent naming — Name external systems to indicate both the platform and environment (e.g., “n8n Production” vs “n8n Development”). This prevents accidentally connecting to the wrong environment.

2. Keep abbreviations short and meaningful — Use standard abbreviations that your team recognizes. These appear in badges and compact displays throughout LMI.

3. Document the purpose in the description — Include information about what integrations use this system, who maintains it, and any special considerations.

4. Separate environments — Create distinct external system entries for development, staging, and production environments. This provides a clear audit trail and prevents cross-environment issues.

5. Secure your credentials — Only users who need to configure integrations should have access to External Systems. Review access periodically and rotate credentials according to your security policies.

Troubleshooting

Adapter cannot find external system

Possible Cause	Solution
External system not created	Navigate to External Systems and verify the system exists. Create it if needed.
Permissions issue	Verify you have permission to view External Systems. Contact your administrator.

External workflow link not working in adapters

Possible Cause	Solution
API URL not configured	Edit the external system and add the API URL (e.g., https://n8n.yourcompany.com).
External ID not set on adapter	Edit the adapter and enter the workflow identifier from your external platform.
Incorrect API URL format	Verify the URL is correct and accessible. Do not include trailing slashes.

Authentication failures in integrations

Possible Cause	Solution
Incorrect credentials	Verify username/password or API token in the external system settings. Test credentials directly in the external platform.
Credentials expired	Check if the external system requires credential rotation. Update the API token or password.
Wrong authentication method	Confirm whether the external system expects Basic Auth (username/password) or Token Auth (API token).

Cannot save external system

Possible Cause	Solution
Required fields missing	Ensure Name, Abbreviation, and Description are all filled in.
Duplicate abbreviation	Check if another external system uses the same abbreviation. Use a unique value.