Skip to Content

next-workflow-builder

DevKit AI Builder Template DocumentationMarketplace
CTRL K
Demo
CTRL K
  • DevKit 
  • AI Builder Template 
    • Introduction
    • Getting Started
    • Configuration
    • Plugins
      • Overview
      • HTTP Request
      • Condition
      • Loop
      • Merge
      • Database Query
      • Run Workflow
      • Run Workflows in Sequence
      • Switch
    • Creating Plugins
    • API Reference
    • CLI Reference
    • Components
    • Database
    • Authentication
    • Deployment
    • Architecture
    • Contributing
    • MCP Server
  • Marketplace
  • Introduction
  • Getting Started
  • Configuration
  • Plugins
    • Overview
    • HTTP Request
    • Condition
    • Loop
    • Merge
    • Database Query
    • Run Workflow
    • Run Workflows in Sequence
    • Switch
  • Creating Plugins
  • API Reference
  • CLI Reference
  • Components
  • Database
  • Authentication
  • Deployment
  • Architecture
  • Contributing
  • MCP Server

On This Page

  • Available Plugins
  • How Built-in Plugins Differ from Marketplace Plugins
  • Using Built-in Plugins
Question? Give us feedback Edit this page 
DocumentationBuilt-in PluginsOverview

Built-in Plugins

Built-in plugins are system actions that ship with next-workflow-builder out of the box. They require no installation or configuration and are available in every workflow.

Unlike marketplace plugins which add third-party integrations, built-in plugins provide core workflow logic and data operations.

Available Plugins

PluginDescriptionCategory
HTTP RequestMake HTTP requests to any API endpointNetwork
ConditionBranch workflow execution based on a conditionFlow Control
LoopIterate over a list of items in batchesFlow Control
MergeCombine data from two inputsData Transformation
SwitchRoute workflow based on rules or valuesFlow Control
Database QueryExecute SQL queries against PostgreSQLData
Run WorkflowExecute another workflow and wait for it to completeOrchestration
Run Workflows in SequenceExecute multiple workflows one after another in orderOrchestration

How Built-in Plugins Differ from Marketplace Plugins

Built-in plugins are part of the System category in the action picker. They differ from marketplace plugins in a few ways:

  • No credentials required (except Database Query, which uses your app’s DATABASE_URL)
  • No installation — always available
  • Hardcoded UI fields — each has a custom React component for configuration rather than using the declarative configFields system
  • Inline code generation — each plugin defines a codeGenerator template used when exporting workflows as TypeScript

Using Built-in Plugins

When creating a workflow, select System from the Service dropdown, then pick the action you need:

  1. Open a workflow in the editor
  2. Add a new action node
  3. Select System as the service category
  4. Choose the built-in plugin from the action dropdown
  5. Configure the plugin fields

All built-in plugins support template references — you can reference outputs from previous nodes using the {{NodeName.field}} syntax or by pressing @ in template input fields.

Last updated on March 12, 2026
PluginsHTTP Request

© 2026 All rights reserved.

Product by David Sanchez