Getting Started

Quickstart

Kemu is a visual workflow platform where you build automations called Recipes by connecting widgets on a canvas. A recipe can run inside Kemu while you build and test it, and it can also be exported as a standalone Node.js application when you are ready to run it elsewhere.

1. Learn the basic concepts

Start with the core building blocks:

  • Composer is the visual editor where you create recipes.
  • Recipes are workflows made from connected widgets.
  • Widgets are typed blocks that receive, transform, store, route, or return data.
  • Ports define how data and events move between widgets.
  • Hub Services provide advanced runtime capabilities and integrations.
  • Edge Export packages a recipe so it can run outside the Composer UI.

Read more in Introduction to Widgets.

2. Create a recipe

Open Composer and create a new recipe. A recipe usually starts with an entry point, passes data through one or more processing widgets, and ends with an output or side effect.

A simple recipe might look like this:

  1. Use an Input Widget to receive data.
  2. Use a Script Widget, Expression Eval Widget, or Template String Widget to process it.
  3. Use an Output Widget to return the result.

3. Connect widgets

Drag widgets onto the canvas and connect their ports. These connections define the event flow of the recipe.

Producer widgets emit events, transformer widgets modify or route data, storage widgets manage shared state, and consumer widgets complete the flow.

See Widget Basics for a deeper explanation of widget roles and connections.

4. Add state or secrets when needed

For shared runtime values, use the Global Variables Panel and Global Variable Widget.

For sensitive values such as API keys, use the Secret Widget with Hub secret mappings. This keeps recipes flexible without hardcoding credentials into the workflow.

5. Run and test

Run the recipe in Composer to confirm that data moves through the widgets as expected. Adjust widget settings, inspect outputs, and refine the flow until the recipe behaves correctly.

For ordering or control flow, see Sequence Widget, If Widget, and Switch Widget.

6. Export when ready

When your recipe is ready to run outside Composer, use Edge Export. This creates a standalone Node.js package that can receive inputs, return outputs, and run your recipe in an external application or deployment environment.