Custom integrations

Set up a custom integration with the Agent when the system you need is not available as a native Lleverage provider.

Industrial operations frequently depend on systems that are not covered by a standard SaaS connector: a customer-specific ERP endpoint, legacy API, internal service or vertical application. In Lleverage this is a custom integration.

Two setup paths

The current Custom API entry point offers two routes:

Custom integration setup can be started as a self-serve form or from the Agent.

• Set it up yourself — fill in the API details and credential setup.

• Let the Agent connect it — describe what needs to be connected in chat and let the Agent guide the setup.

The Agent-led path is often the most natural when you are already defining the work with the Agent. The self-serve path is useful when a builder already has the API details in hand.

Secure credential handoff

The self-serve form captures the integration name, slug, API base URL, credential label, auth method and access scope. Supported auth methods currently include Bearer token, API key header, Basic auth, Query parameter, Custom header, OAuth2 client credentials and NTLM (Windows).

The Custom API setup form immediately before the secure credential-entry handoff.

The next step opens a secure page for the credential value. The credential is stored without needing to appear in Skills or chat. Do not paste API keys or passwords into the Agent conversation, Skill instructions, files or Workflow payloads.

Verify the capability

After setup, verify the intended environment, allowed read/write actions, access scope and the exact action the Agent needs from the correct Project. Treat endpoint, credential and action changes as production authority changes.