Lovable + Noded

Build a Lovable app on Noded as its data layer

A customer portal, an executive cockpit, an internal tool - prompted into existence in Lovable, running on the customer record Noded already keeps from your CRM, support desk, calendar, calls and warehouse. No database to design, no sync code to write. Three steps: connect Noded to the Lovable chat, configure your workspace by conversation, then build the app with the App Builder skill.

Download the App Builder skill The Workspace Setup skill

The short version: add https://app.getnoded.ai/api/mcp/apps to Lovable as a custom MCP chat connector, import the two Noded skills into your Lovable workspace, store a Noded personal access token as a server-only secret, then prompt: "Build a customer portal on Noded for our accounts." The skill discovers your workspace through the connector and generates the server-side calls to the Noded Graph API. The browser never touches Noded.

Before you start

A Noded account with your tools connected - CRM, support desk, email and calendar, data warehouse - under Settings → Integrations.
A Lovable workspace. Custom MCP connectors and custom connectors are available on every plan; a workspace admin turns them on.
A personal access token, created in Noded under Settings → Developer. It is shown once. It acts as the Noded user who created it, so the app sees exactly what that user sees.

The three steps

Connect Noded to the Lovable chat

In Lovable, open Connectors, add a custom MCP server with the URL https://app.getnoded.ai/api/mcp/apps and OAuth, then sign in to Noded and approve. The connection is personal to you and works in the project chat only - it is how Lovable learns what your workspace contains, never how the published app reaches Noded.
Configure your workspace, then add the App Builder

Import the Workspace Setup skill and the App Builder skill under Workspace settings → Skills (upload the zip, or import the folder from GitHub). If your workspace is new, say "Set up my Noded workspace for my business" first: Lovable interviews you, proposes the insights, tables, folders and agent, and builds them with your approval.
Give the app its credential, then prompt

Store the token as NODED_PAT where the app's server side runs: in your own Supabase project under Edge Function secrets after connecting it to the Lovable project, which keeps the token out of Lovable and works on every plan; or in Lovable under More → Cloud → Secrets when the project uses Lovable Cloud; or in the Noded custom connector, created once for the whole workspace so the gateway holds it. Never with a VITE_ prefix, which would send it to the browser. Then describe the app:

"Build a customer portal on Noded for our accounts: their requests, their projects, their invoices, an account review they can generate, and a few preferences they own."

The skill calls the Noded connector to read your Record Types, insights, functions and agents, writes their ids into one config module, and generates one server function or edge-function handler per screen against the Graph API.

What the app can do

Everything the Noded app can do with your data, through the same permission model. Each row is one recipe in the skill, with the exact operation and its rules.

In the app	On Noded
Show and edit insights	The insights your workspace watches on every account, with their history. An edit becomes an override with a reason and an optional expiry; the AI's answer stays behind it.
Read and create records	Live reads from your CRM, support desk or warehouse through a Record Type - the contract that decides which fields the app may see and write. A create lands in the tool and on the account in one call.
Run a workflow	A function installed in a connected tool, for example a slide deck from a template, with the account as context. The link comes back when it is done.
Start an agent	A run of a Noded agent on one account, with its run log: what it looked at, what it decided, what it drafted.
Show the feed	The recommendations waiting for a person. The app approves notes and records and dismisses the rest; drafts that leave Noded are approved in Noded.
The record itself	Accounts, people, the timeline of calls, emails, meetings and records, and what Noded remembers.

Two complete patterns ship with the skill: a customer portal whose users are your customers, not Noded users, and an executive cockpit for your own team. They read the same record, so a request raised in the portal is on the cockpit within seconds, with no sync code between them.

How it stays safe

Server side only. Every call to Noded runs in a server function or a Supabase edge function. The token is never in the browser, a VITE_ variable, a log or an error message.
One user's view. The token acts as the Noded user who created it and can only reach what that user can see. Revoke it in Settings → Developer and the app stops at once.
Contracts, not tables. Reads and writes go through Record Types, so the fields a customer-facing screen can show are decided in Noded, not hidden in app code.
Scoped from the session. A portal user's account comes from their sign-in, never from the request. The skill keeps an allow-list of fields and record types per screen, enforced on the server.
Every write is attributed. The reason on an insight edit, the requester on a record and the account context on a function run show up in Noded's audit trail.
Rate limited. 120 requests a minute per token. The skill batches account reads so a board does not hit it.

If something's off

Symptom	Fix
Lovable says Noded tools are unavailable	The custom MCP connector isn't attached or signed in, or Custom MCP is off for the workspace. Add it under Connectors and start a new chat.
The app answers 401	The token is missing, expired or revoked. Create a new one in Noded under Settings → Developer and update the `NODED_PAT` secret or the connector.
A field or operation "does not exist"	The generated document names something outside the API's external surface. The skill bundles the schema file; ask Lovable to check the document against it.
A create is refused	The Record Type does not allow create, or a required field is missing. Check the contract in Noded under Settings → Record Types.
"Run now" on an agent is rejected	The account is outside the agent's scope, or the agent is in its cooldown. The message says which.

Stuck? We'll help.

The App Builder skill generates code against the Graph API and discovers your workspace through the Noded MCP server. The Noded & Lovable page has the why; the developers hub has the other ways to build on Noded.

Before you start

The three steps

Connect Noded to the Lovable chat

Configure your workspace, then add the App Builder

Give the app its credential, then prompt

What the app can do

How it stays safe

If something's off