Getting started with NoriaFlow

NoriaFlow lets you build automations visually. Connect a trigger to one or more steps, and they run when the workflow is triggered. No code required, though you can use code when you want to.

Create your account#

Head to the sign-in page and continue with Discord, Twitch, or an email magic link. Accounts are created automatically on first sign-in. There's nothing to fill in.

During the open beta, every feature is unlocked for everyone, free.

Explore the dashboard#

Your workspace has six main destinations: Overview, Workflows, Connections, Messages, Data, and Activity. Browse templates from Workflows. Open Getting started for guides or to replay the optional dashboard tour.

The tutorial explains where things live. It does not connect an account, create a workflow, or publish anything for you.

The big picture#

A workflow is made of nodes connected on a canvas:

• A trigger starts the workflow: manually, on a schedule, through a webhook, or from a connected service's event.
• The following steps do the work: create a value, transform data, send a message, call an API, or send an email.

Your next steps#

1. Try My first workflow. It connects Manual Trigger to Create Value and Text Template. No account or extension is required.
2. Make it yours. Open Create Value, edit the greeting value, and apply the change. Text Template reuses it through {{greeting}}.
3. Simulate and inspect. Use Test, then inspect the last step's output. The expected text is “Hello, Alex! Your first workflow works.” A simulation is separate from a real run.
4. Publish and run. Save your draft and publish it when the checks pass. Click Run for its Manual Trigger, then open Activity to inspect the real execution. Saving a draft does not change the published version.
5. Choose services when needed. Open Connections to manage accounts, bots, and API connections. Add the relevant extension and select its connection in the workflow.

Manage results outside the editor#

Messages holds outgoing messages recorded by your Discord bots. Choose the sending connection and destination before composing; a workflow is optional. Historical content and the current Discord message are shown separately.

Data holds information saved across executions, shared by your workflows at account level. Ordinary values created for one run remain in that run's output. Secrets remain in Connections.

Activity combines live executions, paginated run history, ongoing objects and analytics. Use its workflow and period filters to investigate a result, then return to the relevant editor step.

Connections are your choice. A Discord server workflow needs a Discord bot; Twitch workflows use a Twitch account; X actions use the X API connection setup. Follow the guide for the service you want to use.

Stuck? Ask in our community. The fastest way to get help is the NoriaFlow Discord, linked from the contact page.

Setup checks and next steps#

• Check the draft before activating it; saving edits and publishing them are separate actions.
• Resolve missing parameters and connection errors in the workflow that reports them.

See the extension setup guide for adding and reusing services, the node reference for parameters, and testing and debugging for execution diagnostics.