NoriaFlowFree beta
Start building

Build bots and automate workflows across your favorite platforms.

ProductFeaturesPlatformsTemplatesDocsPricing
Log inStart building
All docs

Getting started

Build your first workflow

Create and test a two-step workflow using built-in nodes, without connecting an external account.

2 min read

You will build Manual Trigger → Create Value. When tested, the workflow creates a greeting that you can inspect in its execution output.

Create a blank workflow

  1. Open Workflows and choose New workflow if the creation dialog is not already open.
  2. Start with a blank canvas, name it My first workflow, and choose Create workflow.
  3. The editor opens on your draft. You can also take the optional Dashboard tutorial whenever you want to explore the rest of the workspace.

Add a Manual Trigger

  1. Open Build in the editor sidebar.
  2. Search for Manual Trigger and add it to the canvas.
  3. Leave Input data empty for this example.

A manual trigger starts when you request a run. It does not listen for a service event or run on a schedule.

Create a named value

  1. In Build, search for Create Value. It may also be labelled Create or change a value in the beginner view.
  2. Add it beside the trigger.
  3. Connect the trigger's On Trigger execution output to the value step's Execute input.
  4. Select the value step. Under What should NoriaFlow create?, add one Name | Value row:
NameValue
greetingHello, NoriaFlow!

The name identifies the value for later steps in the same run. You could reuse it as {{greeting}} when adding another step.

Test and inspect the result

  1. Click Test in the editor toolbar to simulate the current draft.
  2. Wait for the two steps to complete.
  3. Open Activity, select the test execution, and inspect the Create Value step's output. Its greeting value should be Hello, NoriaFlow!.

If the value step does not run, check the execution wire between On Trigger and Execute. If validation asks for a value, make sure the row has both the name and the text shown above. Diagnose lists issues in the draft.

Saving and publishing are separate actions. You can keep this example as a draft. Publishing it does not make the manual trigger run automatically; it remains an automation you start yourself.

Add services when your idea needs them

Use Connections to manage the accounts or credentials your next workflow needs, and Extensions to add its service nodes. Each service step has its own requirements.

For an optional Discord example, try the Discord Welcome Message template after connecting a Discord bot. You can instead choose Twitch, X, HTTP, or another supported service for your next automation.

Continue with triggers and actions, extension setup, or testing and debugging.