Writer, 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 Writer 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.
- Artificial Intelligence
- Connects with a key
- 13 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Writer is
Writer is a full-stack generative AI platform for enterprises, offering tools to build and deploy AI applications integrated with their suite of LLMs, graph-based RAG tools, and AI guardrails.
You paste in a key from your own Writer account. It is kept encrypted, and you can withdraw it from inside Writer whenever you like.
One message in, the work done in Writer.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Writer. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Writer account, inside the access you granted it, doing the thing you asked for.
- 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.
What it can do in Writer
These are the ready-made tools your AI employee already has in Writer. It is not limited to them, but it never has to be taught these.
- Ask Question to Knowledge GraphTool to send a question to the knowledge graph and retrieve the answer. use after defining your question and optional context.
- Chat CompletionTool to generate chat-based completions. use when you need conversational ai responses; call after assembling system and user messages.
- Create Knowledge GraphTool to create a new knowledge graph. use after defining nodes and edges to persist the graph.
- Delete GraphTool to delete a knowledge graph by its id. use when you need to remove a graph after confirming its identifier.
- List ApplicationsTool to list all no-code agent applications. use when you need to retrieve all registered applications.
- List FilesTool to list all uploaded files. use when you need to retrieve a paginated set of user files, optionally filtered by status, graph, or type. use after uploading files to inspect av
- List Knowledge GraphsTool to retrieve a list of knowledge graphs. use when you need an overview of existing graphs.
- List ModelsTool to list all available language models. use when you need to discover which models can be used for completions.
- Medical Text ComprehensionTool to extract medical entities and concepts from unstructured clinical text. use when you need to label medical text with standardized codes such as snomed ct.
- Retrieve Knowledge GraphTool to retrieve a knowledge graph by its id. use when you need details of an existing graph.
- Text GenerationTool to generate text based on a given prompt. use when you need model-driven completions after crafting a prompt.
- Update Knowledge GraphTool to update an existing knowledge graph. use after confirming the graph id. specify at least one of name, data, or description to modify.
- Web SearchTool to perform a web search. use when you need relevant web page results for a given query.
You stay the boss of your Writer 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 Writer 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 Writer is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Writer 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 Writer
- Can an AI employee really work inside Writer?
- Yes. It signs in to your own Writer 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 Writer?
- No. Nothing moves and nothing is replaced. Your records stay in Writer, 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 Writer account?
- You paste in a key from your own Writer account. It is kept encrypted, and you can withdraw it from inside Writer 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 Writer?
- It has 13 ready-made tools in Writer today, among them Ask Question to Knowledge Graph, Chat Completion and Create Knowledge Graph. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Writer 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 Writer 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 Writer?
- 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 Writer is written down with what it did and when.