# Documentation - nodulz

Source: https://nodulz.com/docs

Language: en

nodulz is a visual workflow orchestrator. Connect triggers, actions, transformations and AI components to automate operations.

## Choose a path

- **Create your first automation**: follow [Getting started](/docs/getting-started). Process a request and test both branches without an API key.
- **Build a reliable workflow**: read [Workflows](/docs/workflows) to choose a trigger, process a list and move from testing to publication.
- **Reuse data**: open [Expressions and data](/docs/expressions) to understand `input`, node outputs and the differences between text, objects and lists.
- **Process several items**: follow [Process a list](/docs/working-with-lists) to select active contacts and prepare a message for each one.
- **Connect a service**: start from its [node page](/docs/nodes), then prepare the right access with [Credentials](/docs/credentials).
- **Understand a failure**: use [Troubleshooting and FAQ](/docs/troubleshooting) by symptom, then [Executions and logs](/docs/executions) for retries and approvals.

To evaluate nodulz before starting, read [Choosing a workflow tool](/docs/choosing-workflow-tool). For account plans and entitlements, see [Pricing and licenses](/docs/pricing).

## Understand a workflow

A trigger supplies the original input: a webhook request, an application event or manual test data. Actions and transformations then produce outputs that later steps can read.

For example, a webhook receives a request, a node prepares its fields, an IF checks a condition and an integration creates the contact. To verify this flow, inspect the received data, executed branch and contact actually created.

Node pages list technical parameters and configuration guidance. Guides explain how to use them together; start there if you do not yet know which node to choose.

## Find information

Search covers guide content, nodes and credential procedures. Search for a symptom (`empty expression`), task (`HTTP request`), service or technical key (`returnOnlyBody`). Accents and case do not prevent matches.

Examples use technical names such as `http1` and `set1`. Adapt them to the names offered by your workflow’s mapping and always inspect actual output after a test.

## Documentation status

Parameter references come from the nodulz repository’s catalog and schemas. An initial configuration describes catalog defaults: it is not necessarily ready to run. Guided examples specify the settings to complete and the result to check.

Provider capabilities and permissions depend on your account. Credential procedures link to official references; no model or access is guaranteed by its presence in an example.

Installation, Security and API/MCP pages remain reserved. They do not yet provide procedures. Use the paths above to build and diagnose workflows.

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)