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:
| Area | Description |
|---|---|
| Sidebar (left) | Navigation between sections. Collapses to icon-only mode. |
| Topbar (top) | Search, date filters, theme toggle, and your account menu. |
| Main area | The content of the currently selected page. |
4. Core Workflow
Section titled “4. Core Workflow”A typical Nexomatic automation follows this sequence:
(Webhook, Every day at…, EventGrid)"] H["Hub"] A["Sink Agent
(your infrastructure)"] T["Your Task
(Python / PowerShell)"] S --> H --> A --> T
- Set up a sink node — on the Nodes screen, create a node for each machine that will run your tasks, then install the agent service on that machine with the node’s credentials. The node flips to Online once the agent connects. See Sinks & Placement and Installing Sinks.
- Define Library Modules (optional) — the individual code units your own Actions will reference. Platform libraries are ready to use as-is. See Actions & Libraries.
- Create an Action (optional) — reference a library module as its executable code and configure its runtime parameters. Skip this when a platform library already covers the task.
- Set up a Source — create the trigger: a webhook, a cron schedule (the Every day at… preset), an MCP endpoint, or a file watcher. See Sources.
- Create a Flow — on the Flows screen, pick its sources (the triggers), the action, and where it runs (a sink, any matching node, or platform); then add follow-ups for what happens next on success or failure. The grid is the default view — creating or opening a flow slides the editor in.
- Watch it run — monitor execution on the Runs and Traces screens; fan-out branches trace back to one run. Test this flow in the editor fires one real test event before you enable the flow.
5. Next Steps
Section titled “5. Next Steps”- Architecture Overview — understand how the pieces connect.
- Core Concepts — deep-dive on Flows, Actions, Sources, Sinks, and Secrets.
- Sinks & Placement — create the sink node your agents need.
- Actions & Libraries — set up the code modules your automations run.
- Install a Sink on Windows
- Install a Sink on Linux
- Install a Sink in Kubernetes