Connect data sources and APIs

Aim: Add your system APIs to the application context via the Data tab, so that all subsequent prompts can produce UI and logic that correctly references real data structures, field names, and operation types.

Why data connection comes before deep logic generation

Naia Bauild shares API schema metadata (field names, types, operation types) with the AI model on every request once APIs are added. This means prompts like Show a list of work orders sorted by priority. will produce correctly typed, properly bound components rather than generic placeholder code. Connect your APIs early and every subsequent prompt benefits automatically.

Prerequisites

Procedure

  1. Open the Data tab. This is where you manage all data sources, API connections, and data bindings for your application.

  2. Add an API operation by selecting Add API and select from API definitions already configured in the Neptune DXP - Open Edition API Designer that you want Naia Build to be aware of, (for example, GET /workorders, POST /workorders/{id}/status).

    Only field names and types are shared with the AI. Endpoint URLs, credentials, and response data are never transmitted. For more information, see Security and data.

    If your application integrates with SAP, add these through the MultiModel component. The Data tab supports SAP API operations alongside standard REST APIs. Naia Build automatically understands how to bind UI components to MultiModel data structures once they are present in the context.

  3. Confirm APIs are visible in context.

    After adding APIs, in the Chat tab, enter a prompt such as What data sources are available in this application? to confirm that Naia Build can see and correctly describe your connected APIs. This is a quick sanity check before investing in logic generation prompts.

  4. Prompt Naia Build to generate or update UI components that reference your real data. Enter a prompt such as, for example, Create a list view on the Work Orders page that displays work order ID, status, and assigned technician from the work orders API.

    Result: Naia Build uses the schema metadata to produce correctly bound components.

Naia Build operates within the context of a single application per session. If you need to reference data structures from another Neptune application, those must be exposed via an API that is explicitly added to this application’s Data tab.

Result

  • Your system APIs are connected and visible to Naia Build via the Data tab. Subsequent prompts will produce UI components and logic that correctly reference your real data structures, field names, and operation types.

Next steps

Related topics