Docs / Start here / The platform / Chat
Chat
Chat is where you ask OAIZ to build and change workflows, databases and apps, and to explain what happened in your runs and events.
Each chat is one conversation with OAIZ. You write a request, and Chat answers, uses tools and shows what it did as it works. Chat acts with your own access, so it reaches the workflows, documents, databases and integrations you can use. The same conversation also opens as a panel beside other pages, such as a workflow’s canvas.
What Chat does
- Build a workflow
- Describe the work in your own words. Chat plans the workflow, adds its jobs and saves it as a new workflow with a draft. Nothing runs on live events until you select Go live. From a sentence to a workflow walks through one example.
- Change a workflow
- Ask for a change to a workflow you can edit. Chat writes the change to a draft, never to the live version, and asks you to review it in the conversation.
- Ask about runs and events
- Chat searches and reads events and run records, and explains what a job received, what it returned and why it failed. Explain in chat in Logs starts a conversation about one job.
- Test
- Chat can test a workflow or a job with an example event and show the result in the conversation. Its tests do not publish output events. Before a test sends real integration writes, Chat asks you to allow it.
- Knowledge documents and databases
- Chat writes and edits knowledge documents, and can create a database, change its tables, and read or write its rows.
- Apps
- Create an app from a request and change its files in a draft beside a live preview. Chat never publishes the app.
- Web research
- Chat searches the web and reads pages when a request needs outside information.
- Access and Teams
- Chat can propose changes to who has access to an item, and to people and Teams. These changes always wait for your answer on a card.
The composer
The composer is the message box at the bottom of Chat. Below the text field are the mode button, Add context, the model button and Attach files. While Chat responds, the send button becomes Stop generation.
- Tagging with @
- Type @, choose a category and pick an item to add it to the message as context. The categories are Events, Jobs, Logs, Workflows, Knowledge, Databases and Apps. Logs are run records. Add context opens the same categories with search and filters. Dragging a job from the canvas onto Chat adds it too. Tagged items appear above the composer, where you can remove them.
- Attachments
- Attach files with the paperclip, by dropping them on Chat or by pasting. Chat accepts images (PNG, JPEG, WebP, GIF, HEIC), PDF, text, Markdown, HTML, XML, CSV, Excel workbooks, Word documents and PowerPoint presentations, up to 25 MB per file. If the chosen model does not read a format, the composer warns that some attachments will not work.
- Voice input
- The microphone button writes what you say into the composer and sends it 2 seconds after you stop. Typing, clicking in the composer or pressing Escape cancels the send so you can edit the text first.
- Voice conversation
- When the composer is empty, the send button offers Start a voice conversation. You talk with Chat aloud, and its spoken replies appear as Said aloud. Requests that need work run as ordinary chat turns with the same mode, model, tools and approvals. End stops the conversation, and the microphone button mutes you.
Modes
A mode decides which tools, agents and knowledge documents Chat uses and which model answers. The mode button in the composer shows the active mode. A new chat starts in Auto.
- Auto
- Chat, research and build in one mode. Auto has the workflow, job and knowledge agents, event and run search, database tools and web research. It starts with no integration tools and asks for one when a request needs it.
- Plan
- Drafts a plan beside the conversation before any work starts. You can edit the plan text, read its To-dos and see its Allowed tools, which the plan uses without asking for access. Execute plan starts the work and Pause stops it, in the plan workspace and on the plan’s card in the conversation. The card also has View plan and, after a pause, Resume plan and Discard plan. Chat can suggest switching to Plan when a request fits it.
- Custom modes
- Modes you create and name. They belong to you and appear in your mode menu below the built-in modes.
Manage modes, or the settings button beside a mode, opens the Mode studio. Its sections are Model, Execution, Native Tools, Integration Tools, Builder Agents and Knowledge, plus Identity for a custom mode. Changes apply to the current chat at once, and a dot on the mode button marks unsaved changes. Save as mode turns changes to Auto or Plan into a custom mode. Save mode updates a custom mode. Reset changes returns to the saved mode, and Delete mode removes a custom mode permanently.
Model
The model button shows the provider logo of the model that answers in this chat. Its menu offers Default, which uses your organisation’s default chat model, Fast and a third preset described as Most capable. Fast and the third preset appear when your organisation has set those models and permits them in Chat.
More models opens the full list with search. Each model shows its capabilities, context window, estimated speed, estimated usage cost per million tokens and whether it runs on OAIZ or on your organisation’s own key. The list contains only models your organisation permits in Chat, as described in Bring your own key. The choice applies to the current chat, and saving a custom mode keeps it.
Tool approval
Each tool in a mode has an approval setting in the Native Tools and Integration Tools sections of the Mode studio. A newly added tool starts at Run automatically. An integration’s tools can be set together, and the group shows Mixed approvals when they differ.
- Run automatically
- The tool runs without a card.
- Run after 5 seconds
- A card counts down for 5 seconds. Decline stops the call, otherwise it runs.
- Ask before running
- The call waits until you choose Allow or Decline on its card.
Change access and Change people and Teams show Always asks instead of a setting. They wait for your answer in every mode. After a Decline, Chat chooses a different approach. Some cards also offer Allow all read tools or Allow all write tool access, which allows every read or write tool of that integration for the rest of the chat.
Cards in the conversation
When Chat needs something only you can give, it pauses and shows a card in the conversation. The request continues after you answer.
- Connect an integration
- Appears when a request needs a service you have not connected. Connect opens the same connection dialog as Integrations, and Chat continues with the new integration. Cancel lets Chat continue without it.
- Tool access requested
- Appears when Chat needs a tool your organisation has but the current mode lacks. Allow adds that tool to the chat. Decline refuses it.
- Give access
- Appears when a job Chat saved needs access to documents, databases or integrations. Access control explains the rows and what Allow gives.
- Change access
- Shows the current and proposed access for each item. When access is lowered, it lists the live workflows that can stop working, and nothing is paused for you. Nothing changes until you allow it, and Access control explains who can change access.
Reviewing workflow changes
After Chat edits an existing workflow, a bar above the composer sums up the edit, such as Made 3 changes and 1 job added. By then the edit is already saved as a new version of the draft.
- View changes
- Opens the draft on the canvas at the first changed job. Changed fields are marked, and the job shows each field’s previous value.
- Keep changes
- Keeps the new version and closes the bar. It opens the draft if you are not already on it.
- Reject changes
- Saves the version before the edit again as the latest version of the draft. The rejected version stays in the version history.
Reject changes works only while the edit is the latest version of the draft. After a newer edit, Chat reports that it cannot reject the edit. The first generation of a new workflow has no review bar, because it is the draft’s first version. Workflows explains how to discard or restore a draft.
Chat history
New chat, the plus button in the Chat header, starts an empty conversation. History, the clock button, opens Chat history with your own chats, newest first. Each entry shows the chat’s title, when its last message was sent and its message count. Search chats matches titles. Opening a chat continues the conversation where it stopped. Each chat has its own address, so a link opens that conversation.
Templates
An empty chat shows Browse templates. It opens the Template Library, where you search templates by name, category or integration and filter by use case and integration. Each template shows its publisher, a video or workflow preview, the integrations and knowledge documents it needs, and About this template.
Use template opens a new workflow with an import summary of the integrations and knowledge documents the template uses. Import template creates the workflow as a draft and copies its knowledge documents into your organisation. Required integrations are matched to your own, and unmatched ones can be finished in the builder.