Inistate
for LuumenAI
Read Inistate modules and records, then change entries as approved steps
Connect Inistate and the agent can read your workspaces, module schemas, saved listings, and individual records, including the full audit trail behind a change. When something needs to move, it drafts the update or state transition against the module's own activity, shows you the fields it will send, and waits for your approval before submitting.
The Inistate toolbox
12 tools: 7 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Activity FormGet the required fields, current values, options, defaults, and confidence threshold for a module activity before submitting it.
- ReadGet EntryGet one module record by ID, including its current values, state, audit metadata, and available activities.
- ReadGet Entry HistoryReturn one chronological 50-item page of a record's audit trail, comments, field changes, and AI traceability context.
- ReadGet Module SchemaGet a module's fields and states, optionally including its activities and flows, before querying or changing records.
- ReadList EntriesReturn one page of records from a module using a saved listing, field filters, search, sorting, and field projection.
- ReadList ModulesList modules available in a workspace so their exact names can be used in schema and record tools.
- ReadList WorkspacesList workspaces accessible to the connected API key, optionally filtering by workspace name.
- WriteBulk Change Entry StatesRequest state transitions for 1-100 entries in one module. Approval by default
- WriteBulk Update EntriesUpdate fields on 1-100 entries in one module. Approval by default
- WriteChange Entry StateRequest a state transition for one module record; low confidence can flag the result and suppress the transition. Approval by default
- WriteCreate EntryCreate one record in a module through its create activity and return whether low confidence caused it to be flagged. Approval by default
- WriteUpdate EntryUpdate fields on one existing module record through its edit activity and return whether low confidence caused it to be flagged. Approval by default
One prompt, start to finish
What a governed Inistate run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — bulk change entry states, bulk update entries, change entry state, create entry, and more — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Inistate — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Inistate to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.