Intake → structured run
A form or trigger starts a run with owners, fields, and the next step already defined.
Nodes used
- TRIGGER
- FORM_INPUT
- USER_SELECTION
- AUTOMATION
Production-grade nodes: people, Google Workspace, data, webhooks, and governed AI. Integration is not a slide deck—it is execution with traceability.
A form or trigger starts a run with owners, fields, and the next step already defined.
Human decisions chain to Gmail, in-app alerts, and a traceable record on the run.
Upload a dump, normalize and validate, then write to Sheets or a Data Source the rest of NitroFlow reads.
Browse the full node catalog below—people steps, Google Workspace, data pipeline, automation, and flow control. Each node runs inside a workflow with the same audit trail.
Steps a human completes: decisions, data, and visible tasks.
Configurable states and a clear decision trail.
Structured capture in the context of the run.
Task lists with an explicit completion signal.
Pick owners with role-aware rules.
One selection with flow branches.
Several options in one step.
Dates with validation and templates.
Free or guided text according to rules.
Pick values from a governed source.
Automations on the stack your company already uses.
Send and chain email automation.
Google Workspace
Folders and files as part of the flow.
Google Workspace
Documents from templates and run data.
Google Workspace
Read and write spreadsheets.
Google Workspace
Generated or updated decks.
Google Workspace
Events and time coordination.
Google Workspace
Ingest, clean, and write to Data Sources.
Upload CSV/XLS into the operational pipeline.
Consume raw or derived layers.
Write governed outputs back.
Consistent formats per column.
Explicit rules before moving on.
Tokenize values into new columns.
Summarize and group without fragile spreadsheets.
Keys and merge strategies you can explain.
Connectors, scheduling, and notifications.
Outbound HTTP calls with run payload.
Rules on status changes and steps.
In-app and email on a schedule or event.
Start via form, webhook, file, calendar, or manual.
Branching and composing workflows.
Branches based on run data.
Multiple paths from one field.
Nest another project with inherited context.
Models with context and limits; works with providers you already use.
Text (and image where configured) with prompt, context, and provider.
OpenAI · Google Gemini · Anthropic · OpenRouter
No—it integrates with them. Nodes perform actions on tools you already use; AI runs with flow context, not in a vacuum.
Steps, allowed data, audit trails, and limits: people and AI follow the same operational contract.
Leave your email and we will guide you to access.