Keep the automations. Add the business workflow you should not rebuild for every client.
Your n8n workflows execute. Inistate holds the state, the permitted next activities, the typed forms, the ownership and the history around them — so what you ship is an operational system people can run, not another dashboard you maintain.
n8n-nodes-inistate is a verified community node, installable on n8n Cloud and self-hosted.
Stop rebuilding the same six things
The automation is the part you enjoy. Then comes the operational layer around it, and you build it again from scratch on the next project.
State and tables
A place to keep the thing the process is about, and a status column that only means something if everyone remembers the convention.
Forms and required fields
One for each step, each with its own validation, each drifting out of step with the workflow that consumes it.
Approvals and role rules
Who may act, at which step, on which record. Usually branches and conditionals that nobody else can safely change.
Exception handling
The happy path is an afternoon. The reassignments, the corrections and the things that stall are the rest of the project.
An operator surface
The client needs to see and act on work from a phone. That is an app, and now you own it.
History somebody can read
Execution logs answer what the workflow did. They do not answer what happened to this job, in order, and who acted.
One primitive, instead of conventions
Execution workflows are not automatically the authoritative business lifecycle, or the operator’s shared work surface. Inistate gives the process an explicit one.
State → Activity (Form) → State. The same contract whether a person, an AI agent or an n8n workflow performs the activity.
Seven operations, and no arbitrary writes
The node does not hand your workflow a generic update endpoint. It asks the record what is permitted now, and performs one of those activities.
Create record
Start a job, case, request or claim from anything n8n can trigger on.
Get record and state
Read where the work stands before deciding what your workflow should do next.
List allowed activities
Ask the server what this record permits right now, for this actor, in this state.
Execute activity
Perform one permitted activity with its typed payload. The server validates and transitions.
Update permitted fields
Change what this actor is allowed to change, without stepping outside the transition contract.
Search, list, and trigger on change
Find records, and start an n8n workflow when one of them moves.
What your client ends up running
A web and mobile operator surface comes with the workflow, so the part you would otherwise build and then maintain is not yours to own.
Visibility
Where is it? One current state per record, on desktop and on a phone.
Control
What is allowed now? The permitted activities come from the state, not from the actor.
Coordination
Who or what needs to act? Ownership sits on the record, and so does the thing it is waiting for.
Accountability
What happened before? Business-object history across executions and actors, not a pile of run logs.
The same contract for the agent you are adding
Give your AI agent permitted business activities, not unrestricted record access. The agent reasons. Inistate determines what it may do now.
An agent reaches Inistate over MCP or the API, asks the record what it may do in its current state, and performs one of those activities through the same form and the same validation a person would use. What it did, on what basis, and how sure it was land on the record beside everything else.Same primitive. Different interface.
Keep n8n. Keep Claude. Give them one business workflow.
Automation platforms execute. AI reasons. Inistate owns the business lifecycle and determines what the process permits now. Nothing here asks you to move execution, and Inistate is designed so the business workflow can stay stable even when the actor changes.
Build your first Inistate + n8n workflow
Free forever for small teams. Install the node, start from a template, and put one real process behind it.