Skip to main content
The jam-nodes Playground provides two ways to test nodes interactively:
  • CLI - A command-line tool for quick testing during development
  • Web - A browser-based UI for visual exploration and demos

​
When to Use Each

Use CaseCLIWeb
Testing nodes during developmentBestGood
Exploring node inputs/outputsGoodBest
CI/CD or scripted testingBest-
Demos and presentations-Best
Learning the node APIGoodBest

​
Installation

npm install -g @jam-nodes/playground

npx @jam-nodes/playground list

git clone https://github.com/wespreadjam/jam-nodes
cd jam-nodes/packages/playground-web
npm install && npm run dev

​
Quick Examples

List all available nodes: 
jam list
Run a node with mock data (no API keys needed): 
jam run delay --mock
Run a node with JSON input: 
jam run conditional -i '{"condition":{"type":"equals","variableName":"x","value":"y"},"trueNodeId":"a","falseNodeId":"b"}'

​
Credential Management

Both CLI and Web interfaces support three credential sources:
  1. Environment variables - Most secure, recommended for production
  2. Encrypted local storage - Convenient for development
  3. Runtime prompts - One-off testing
Use jam init to generate an .env template with all supported credentials.

​
Next Steps

CLI Reference

Full command reference for the CLI tool.

Web Playground

Guide to the browser-based playground.