Adapters

Adapters serve as automation connectors between LMI and external systems. They enable bi-directional communication with workflow automation platforms like n8n, Make, or Zapier, allowing you to trigger external workflows and receive inbound requests.

Overview

The Adapters module allows you to:

• Register automation endpoints that connect LMI to external systems
• Configure webhook URLs for outbound data transmission
• Optionally expose API endpoints for inbound requests from external systems
• Link adapters to configured external systems for organization and quick access
• Navigate directly to external workflow configurations when External IDs are set

Accessing Adapters

Navigate to Settings → Data Integration → Adapters from the sidebar menu.

Note

Access to Adapters requires the ADAPTERS role. Contact your administrator if you don’t see this option in the menu.

Adapters List

The adapters list displays all automation connectors configured for your organization.

Table Columns

Column	Description
Name	The adapter name. Click to open the edit panel.
Event Name	The internal event identifier for this automation.
System	The linked external system, displayed as a badge. Click to navigate to the external workflow (when External ID is configured).
Automation URL	The webhook URL (truncated). Click to copy the full URL to clipboard.

Searching Adapters

Use the search field in the header to filter adapters by name.

Viewing Adapter Details

Click on any adapter name in the list to open the detail panel. The adapter edit panel displays all configuration options in a slide-out sheet.

Registering a New Adapter

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

Adapter Fields

Field	Required	Description
Automation Name	Yes	A descriptive name for the adapter. Automatically converted to CONSTANT_CASE format (e.g., “Order Created” becomes “ORDER_CREATED”).
External System	Yes	The external platform this adapter connects to. Select from configured External Systems.
External ID	No	The workflow or automation identifier in the external system. When set, enables direct navigation to the external workflow from the list view.
Event Name	No	A unique identifier for this automation event. Useful for organizing and referencing adapters programmatically.
Automation URL	Yes	The webhook URL where LMI sends data when the adapter is triggered. This is typically provided by your external automation platform.

Tip

Before saving, verify your webhook URL by testing it in your external automation platform. Most platforms provide a test or debug mode for webhook endpoints.

Editing an Adapter

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

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

Configuring API Access

Adapters can optionally expose an API endpoint that external systems can call to trigger the automation. This enables bi-directional communication where external systems can both receive data from LMI (via webhook) and send data to LMI (via the exposed endpoint).

Enabling API Access

1. Open an existing adapter (the adapter must be saved first)
2. Locate the Enable API Access toggle in the edit panel
3. Toggle the switch to On
4. Select the HTTP Verb (GET or POST)
5. Copy the generated API endpoint URL

Caution

Exposed API endpoints require Basic Authentication. Share your credentials securely with the external system that will call this endpoint. Never expose credentials in public repositories or logs.

API Access Fields

Field	Description
Enable API Access	Toggle to expose or hide the adapter’s API endpoint.
HTTP Verb	The HTTP method the endpoint accepts (GET or POST). Choose based on your external system’s requirements.
API Endpoint	The generated URL that external systems can call. Click the copy button to copy to clipboard.

Disabling API Access

Toggle the Enable API Access switch to Off. The API endpoint will immediately stop accepting requests. You can re-enable it at any time.

Relationships

Adapters connect to External Systems to organize your integrations and enable quick navigation to external workflow configurations.

┌─────────────────────────────────────────────────────────┐
│                    External System                       │
│  (e.g., n8n, Make, Zapier)                              │
│                                                          │
│  - API URL                                               │
│  - Credentials                                           │
└─────────────────────────────────────────────────────────┘
                           │
                           │ belongs to
                           ▼
┌─────────────────────────────────────────────────────────┐
│                        Adapter                           │
│                                                          │
│  - Automation Name                                       │
│  - External ID (optional link to workflow)               │
│  - Webhook URL (outbound)                                │
│  - API Endpoint (optional inbound)                       │
└─────────────────────────────────────────────────────────┘

Related Features

• External Systems — Configure the external platforms that adapters connect to
• Webhooks — Send notifications when events occur in LMI
• Subscriptions — Subscribe to specific events in the system

Best Practices

1. Use descriptive names — Name adapters clearly to indicate their purpose (e.g., “Dispatch Notification” rather than “Adapter 1”). The name is automatically formatted to CONSTANT_CASE.

2. Configure External IDs — When your external platform provides workflow identifiers, set the External ID field. This enables one-click navigation from the adapters list to the external workflow.

3. Test before production — Verify webhook URLs work correctly in a test environment before connecting production systems.

4. Enable API access only when needed — Only expose API endpoints when bi-directional communication is required. Fewer exposed endpoints reduce your security surface.

5. Document your integrations — Keep a record of which adapters connect to which external workflows, including any transformation logic applied in the external system.

Troubleshooting

Adapter not triggering external workflow

Possible Cause	Solution
Incorrect webhook URL	Verify the URL is correct and the external workflow is active. Test the URL using your platform’s debugging tools.
External system offline	Check the status of your external automation platform.
Authentication failure	Ensure any required authentication headers or tokens are configured in the external system.

API endpoint returning errors

Possible Cause	Solution
API access not enabled	Open the adapter and verify the Enable API Access toggle is on.
Invalid credentials	Confirm you’re using the correct Basic Auth credentials.
Wrong HTTP verb	Check that you’re using the same HTTP method (GET or POST) configured in the adapter.
Adapter webhook URL missing	The adapter must have a webhook URL configured before API access can be enabled.

External System badge not clickable

Possible Cause	Solution
External ID not set	Edit the adapter and enter the workflow identifier from your external system.
External System API URL not configured	Verify the linked External System has an API URL configured in External Systems.

Cannot save adapter

Possible Cause	Solution
Required fields missing	Ensure Automation Name, External System, and Automation URL are all filled in.
Invalid URL format	Verify the Automation URL is a valid URL starting with http:// or https://.