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
| Plugin | Description | Category |
|---|---|---|
| HTTP Request | Make HTTP requests to any API endpoint | Network |
| Condition | Branch workflow execution based on a condition | Flow Control |
| Loop | Iterate over a list of items in batches | Flow Control |
| Merge | Combine data from two inputs | Data Transformation |
| Switch | Route workflow based on rules or values | Flow Control |
| Database Query | Execute SQL queries against PostgreSQL | Data |
| Run Workflow | Execute another workflow and wait for it to complete | Orchestration |
| Run Workflows in Sequence | Execute multiple workflows one after another in order | Orchestration |
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
configFieldssystem - Inline code generation — each plugin defines a
codeGeneratortemplate 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:
- Open a workflow in the editor
- Add a new action node
- Select System as the service category
- Choose the built-in plugin from the action dropdown
- 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