Skip to content
Nexomatic Docs

Getting Started

This guide walks you from a fresh account to your first running automation.

1. Create an Account

Section titled “1. Create an Account”

Open the Nexomatic web application in your browser. On first load you will see the login screen.

Joining the team

Section titled “Joining the team”

An Admin can invite you from the User Management screen. You will receive an email with a registration link. Opening that link pre-fills the invite token — after registering you can log in immediately.

First user (new installation)

Section titled “First user (new installation)”

If no users exist yet, clicking Register creates the first account with Admin access. No email verification is required for the first user.

2. Log In

Section titled “2. Log In”

Enter your email and password on the login screen and click Sign In.

If your organisation uses a social provider (Google, Microsoft, GitHub), click the corresponding button and complete the OAuth flow in the pop-up window.

Once authenticated you are taken to the Dashboard.

3. Understand the Layout

Section titled “3. Understand the Layout”

The application has three main areas:

AreaDescription
Sidebar (left)Navigation between sections. Collapses to icon-only mode.
Topbar (top)Search, date filters, theme toggle, and your account menu.
Main areaThe content of the currently selected page.

4. Core Workflow

Section titled “4. Core Workflow”

A typical Nexomatic automation follows this sequence:

flowchart LR S["Event Source
(Webhook, Schedule, EventGrid)"] H["Hub"] A["Sink Agent
(your infrastructure)"] T["Your Task
(Python / PowerShell)"] S --> H --> A --> T
  1. Define a Sink Type — describes the kind of agent that will run your code (Python, PowerShell, etc.) and provides the credentials agents use to connect. See Sink Types & Configuration.
  2. Create a Library — on the Libraries screen, copy a platform template or create your own library, and attach it to your Sink Type.
  3. Define Library Modules — the individual code units (import names) that Actions will reference. See Actions & Libraries.
  4. Create an Action — references a Library Module as its executable code and configures its runtime parameters.
  5. Create a Flow — on the Flows screen, pick a source type (the trigger), a sink type (the target), and your action; then add chain links for what happens next on success or failure.
  6. Install a Sink — deploy the agent process on your Windows server, Linux host, or Kubernetes cluster using the credentials from your Sink Type. See Installing Sinks.
  7. Set up a Source — e.g. configure a webhook URL or cron schedule that fires the Flow.
  8. Watch Events flow — monitor execution on the Events and Logs screens; fan-out branches trace back to one run.

5. Next Steps

Section titled “5. Next Steps”