App Builder

Inistate, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Inistate account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • App Builder
  • Connects with a key
  • 12 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Inistate is

Inistate is a workspace platform for building workflow and record-management applications, configuring modules, managing entries and activities, auditing changes, and handling files.

You paste in a key from your own Inistate account. It is kept encrypted, and you can withdraw it from inside Inistate whenever you like.

How a run works

One message in, the work done in Inistate.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Inistate. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Inistate account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

12 tools it already has

What it can do in Inistate

These are the ready-made tools your AI employee already has in Inistate. It is not limited to them, but it never has to be taught these.

  • Bulk Change Entry StatesRequest state transitions for 1-100 entries in one module. Inistate processes items sequentially and returns fail-soft per-item results; low confidence may flag and suppress indivi
  • Bulk Update EntriesUpdate fields on 1-100 entries in one module. Inistate processes items sequentially and returns fail-soft per-item results, so one failure does not roll back or stop the remaining
  • Change Entry StateRequest a state transition for one module record; low confidence can flag the result and suppress the transition.
  • Create EntryCreate one record in a module through its create activity and return whether low confidence caused it to be flagged.
  • Get Activity FormGet the required fields, current values, options, defaults, and confidence threshold for a module activity before submitting it.
  • Get EntryGet one module record by ID, including its current values, state, audit metadata, and available activities.
  • Get Entry HistoryReturn one chronological 50-item page of a record's audit trail, comments, field changes, and AI traceability context. Pagination is explicit and zero-based because Inistate does n
  • Get Module SchemaGet a module's fields and states, optionally including its activities and flows, before querying or changing records.
  • List EntriesReturn one page of records from a module using a saved listing, field filters, search, sorting, and field projection.
  • List ModulesList modules available in a workspace so their exact names can be used in schema and record tools.
  • List WorkspacesList workspaces accessible to the connected API key, optionally filtering by workspace name.
  • Update EntryUpdate fields on one existing module record through its edit activity and return whether low confidence caused it to be flagged.
Access, and who is in charge of it

You stay the boss of your Inistate account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Inistate account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Inistate is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Inistate and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Inistate

Can an AI employee really work inside Inistate?
Yes. It signs in to your own Inistate account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Inistate?
No. Nothing moves and nothing is replaced. Your records stay in Inistate, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Inistate account?
You paste in a key from your own Inistate account. It is kept encrypted, and you can withdraw it from inside Inistate whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Inistate?
It has 12 ready-made tools in Inistate today, among them Bulk Change Entry States, Bulk Update Entries and Change Entry State. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Inistate and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Inistate and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Inistate?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Inistate is written down with what it did and when.