Sätt att interagera med Lumenbase

    Core Concept

    Använd appen, REST API, OpenClaw, Claude-kopplingar, Zapier och Lumo med samma arbetsytadata.

    Av Sebastian StreiffertPublicerad Jan 10, 2026Uppdaterad May 29, 20268 min läsning

    One workspace, four ways in

    Contacts, companies, deals, tasks, invoices, and activities all live in your workspace. You can work with them in the browser, from your own servers, or through an agent. Same data each time; you just sign in a different way depending on which path you use.

    App UI, REST API, agent frameworks such as OpenClaw and Hermes, and Claude connectors each connect to the same workspace CRM data.

    App UI

    navigation · pages

    People

    Claude

    Custom connector · MCP

    AI agents

    Your workspace

    Same CRM data

    Agent Frameworks

    OpenClaw, Hermes, and remote MCP

    AI agents

    REST API

    HTTPS · JSON

    Your code

    Gmail, Slack, LinkedIn, and similar integrations pull data in from other tools. Personal mailboxes and LinkedIn live under Settings → Personal → Integrations; shared connections like Slack live under Settings → Workspace → Integrations.

    The four ways

    Zapier and Lumo

    Two more pieces that sit alongside the four ways above.

    Outbound events

    When the CRM changes, Zapier can pick it up. See Zapier setup. Configure under Settings → Workspace → Integrations.

    Lumo (in-app)

    The assistant inside the app. It can use the same CRM actions as the Agent API, and you stay signed in as yourself. Lumo guide

    Where to configure

    App UI: Sign in, left menu, Settings for admins
    REST API: Settings → Workspace → API
    Agent Frameworks / MCP: Settings → Personal → Integrations → Agent Frameworks & MCP
    Outbound events: Settings → Workspace → Integrations
    Lumo: Settings → Workspace → Lumo
    REST docs: /api
    Agent API base URL: https://api.lumenbase.io/functions/v1/openclaw-api
    Treat API tokens like passwords. Revoke keys you are done with.

    REST reference: API documentation

    Was this article helpful?