Nembl
Workflows
Builder Overview

Workflow Builder Overview

The workflow builder is Nembl's visual tool for designing how requests are processed. Instead of writing code, you drag and drop phases onto a canvas, connect them with transitions, and define what happens at each step. Workflows automate the path from request submission to completion.

What Is a Workflow?

A workflow is a series of steps (called phases) connected by transitions that define how a request moves through your process. For example, a "New Employee Onboarding" workflow might include phases for manager approval, IT setup, HR paperwork, and a welcome meeting.

Workflows are linked to service offerings. When someone submits a request for that offering, the workflow starts automatically and guides the request through each phase.

The Workflow Canvas

When you open the workflow builder, you see a canvas where you design your workflow visually. The canvas works like a flowchart editor:

  • Phases appear as boxes on the canvas. Each phase represents a step in your process.
  • Transitions are the arrows connecting phases. They define the order in which steps happen.
  • The toolbar on the side has the phase types you can add to the canvas.

You can zoom in and out of the canvas, and pan around to see your entire workflow.

Creating a New Workflow

  1. Go to Admin > Workflows in the sidebar.
  2. Click New Workflow.
  3. Give it a name and an optional description.
  4. The builder opens with a Start phase already on the canvas.

From here, you build your workflow by adding phases and connecting them.

Adding Phases

To add a phase to your workflow:

  1. Click a phase type from the toolbar (for example, Process, Decision, or Parallel).
  2. The phase appears on the canvas.
  3. Drag it to the position you want.
  4. Click on it to configure its settings (name, description, assignments, and more).

See Phases and Transitions for a detailed guide on each phase type.

Connecting Phases with Transitions

To connect two phases:

  1. Hover over the source phase until you see a connection handle.
  2. Click and drag from the handle to the target phase.
  3. Release to create the transition.
  4. Optionally add a label to the transition to describe when this path is taken (for example, "Approved" or "Needs Revision").

Transitions define the flow. A request moves from one phase to the next along these connections.

Saving and Publishing

Workflows have two states:

Draft

When you first create or edit a workflow, it is a draft. You can save your changes at any time without affecting anything else. Drafts are only visible to administrators.

Published

When your workflow is ready to use, click Publish. Publishing creates an immutable, numbered version of the workflow. This version is what runs when requests come in.

Important points about versioning:

  • Editing a published workflow creates a new draft. The published version continues to run unchanged.
  • Requests that are already in progress stay on the workflow version they started with.
  • New requests use the latest published version.
  • You can publish as many versions as you need. Each version is numbered and saved.

Tips for Building Workflows

  • Start simple. Begin with a straightforward linear workflow and add complexity as needed.
  • Name phases clearly. "Manager Approval" is better than "Step 2."
  • Use descriptions. Add details to each phase so the person working on it knows exactly what to do.
  • Test with a sample request. Submit a test request to walk through the workflow and make sure it works as expected.
  • Review before publishing. Once published, a version cannot be changed (only new versions can be created).

Next Steps

Tracking RequestsPhases & Transitions