The different development pathways are summarized in the table below: 

Method of DevelopmentScope of CreationPowered by Nextworld Intelligence
Metadata applicationsSingle metadata recordsNo.
Requires you to create a metadata record then manually configure its fields and components. 
Quick Start options Single metadata records or multiple related metadata records, such as an application, its table, data items, and workflow.  
Yes.
Capable of creating multiple related records at once, but requires you to manually configure the fields and components. 
Prompting Ed in the Developer StudioSingle metadata records or multiple, related metadata records, such as an application, its table, lookups, data items, and workflow. Yes.
Capable of creating multiple related records at once, but requires you to manually configure the fields and components.
Prompting Ed the Builder in Project Builder Single metadata objects or records, or an entire project with an application, tables, fields, logic, workflow, and security. Yes.
Requires no manual configuration. Creates multiple metadata records as well as AI-generated HTML and JavaScript application features which do not follow the standard infrastructure of platform applications. Update and refine a project through prompts entered into Ed the Builder. 

Traditional development

Navigate to individual metadata applications to create components for your application or process, or use the Quick Start options within the Developer Studio.

Quick Start is powered by Nextworld Intelligence, but still requires manual refinement and configuration of the records and components. With Quick Start, you can:

  • Create multiple related metadata records within one process—Create and configure your data items, table, application, and workflow in one location. Nextworld Intelligence creates the metadata records and fills in some of the required fields, such as table name and field selection, based on your selections. 
  • Create applications from a spreadsheet—Create an application over spreadsheet data imported and reviewed by Nextworld Intelligence. The required fields are created and added to the platform table, then data is automatically imported.
  • Create with Ed—Open Ed from the Main Menu bar inside of the Developer Studio. Enter prompts to build metadata such as applications, tables, data items, workflows, interactive reports, and table lookups. Nextworld Intelligence creates the metadata records and fills in some of the required fields. 

Alternately, you can open individual applications, such as the Table Definitions, Data Item Definitions, and Logic Block Builder to create the individual metadata records needed for your applications. 

Learn more in Developer Studio and Quick Start options.

Agentic development 

Use the Project Builder to create entire projects including applications, tables, logic blocks, workflows, and security through AI prompting. Project built applications do not rely on the same infrastructure and requirements as applications built in the Developer Studio applications. You can build with outcome driven prompting, such as "I want a form with a button that navigates users to another form," rather than having to manually create and configure an application link. 

This method does not require manual configuration of the fields and components. Instead, you refine your project through additional prompts entered into Ed the Builder. 

Learn more in Project Builder.



Integrations in Project Builder

This topic describes what integrations you can build with agentic development in Project Builder, including endpoints that send data to external systems and webhooks that receive data from them.

You can build integrations with external systems using traditional development, such as the Endpoint Definitions and Webhook Setup applications, or with agentic development in Project Builder. With agentic development, Ed the Builder creates and configures endpoints that send data and webhooks that receive it from your description, and they can work with data formats beyond JSON. This topic describes what integrations built in Project Builder support, and notes what capabilities are unavailable with traditional development integrations. 

Learn more in Endpoint definitions in Project Builder and Webhooks in Project Builder.

External endpoints

What Project Builder supportsNotes
Describe an endpoint to Ed the Builder and have it configured, including authentication, headers, and parameters.Traditional endpoints are configured manually in the Endpoint Definitions application.
Send any request body as written, such as XML or SOAP, form-urlencoded, plain text, attachments, multipart, or a streamed file.Not supported with traditional endpoints, which build the body as JSON from field mappings.
Read any response as it is returned, as text, a stream, an attachment, or multipart parts.Not supported with traditional endpoints, which map the response to fields.
Call an endpoint from a logic block with a JavaScript SDK. The platform applies the endpoint's authentication, so secrets and tokens can be placed in the request without the logic block seeing them.Endpoints created in Project Builder are called from logic blocks created in Project Builder.
See non-JSON request and response bodies as text in Endpoint Logging.Also available for traditional endpoints.

Webhooks

What Project Builder supportsNotes
Describe a webhook to Ed the Builder and have it created, including the logic that processes each request.Traditional webhooks are configured in the Webhook Definitions and Webhook Setup applications.
Receive form posts, XML, and plain text bodies. The handler gets the raw request.Not supported with traditional webhooks.
Receive CloudEvents and empty bodies.Also available for traditional webhooks.
Verify signatures for vendors that use their own signing scheme, use SHA-1, SHA-256, or SHA-512 HMAC, detect duplicate events using an event ID in the request body, log failed authentication attempts, and reply with a custom acknowledgement.Also available for traditional webhooks.

Using Project Builder logic with traditional logic

Once Project Builder creates a logic block, a traditional logic block can call it with the call logic block action. This lets you use a Project Builder integration from logic you already have.