Changelog

Building in the open

What we ship, every week. Search it, filter it, and share the parts that matter to you.

Watch the demosRSS

21 to 28 Sep 2026Week 3920 updates

Voice and decisions for everyone

Live voice and the decision node leave beta. Databases and Query with AI enter early access.

Shipped

NewChat and voice

Live voice

Talk to OAIZ out loud and hear it answer in real time.

Live voice is a spoken conversation with OAIZ. It listens while you talk, answers out loud, and passes bigger requests to the agent that builds your workflows. Talk time is billed by the second.

How it works
  1. Open an empty chat and press the voice button in the chat box.
  2. Say what you need in your own words.
  3. OAIZ answers out loud, and its words appear under the orb.
  4. For a build or an edit, it hands the request to the workflow agent.
  5. Press End when you are done.
Use it for
  • Describe a workflow while your hands are busy.
  • Talk through an idea before you build it.
  • Make a quick change to a workflow as you talk it through.
NewBuilder

Decision node

Ask a question about each event. Branch the workflow on the answer.

The decision node reads each event and answers questions you write about it, all in one model call. Later jobs filter on those answers, so every ticket, lead, or invoice takes the right branch.

How it works
  1. Add a Decision job and choose which event fields it reads.
  2. Write questions as yes or no, pick one, or a score on your scale.
  3. Connect the follow-up jobs and filter each one on an answer.
  4. Test it on a sample event and check each answer in Logs.
Use it for
  • Route support tickets by urgency and owning team.
  • Qualify inbound leads before they reach sales.
  • Hold back invoices that need a person to check them.
  • Let agents make the same call with the decide tool.
NewAI models

GPT-6 and Claude Opus 5.5

Five more models to pick from, in chat and in any AI job.

The model menu adds GPT-6 Sol, GPT-6 Luna, Claude Opus 5.5, Grok 4.7, and Muse Spark 1.3. GPT-6 Luna is the chat default. The builder also uses it to write jobs and code.

  • Model scores use the updated Artificial Analysis index.
  • Tongyi DeepResearch is deprecated.
How it works
  1. Click the model button under the message field.
  2. Pick a model, or search the list by name.
  3. Give each AI job its own model in the prompt settings.
Use it for
  • GPT-6 Sol when a task needs the most capable model.
  • GPT-6 Luna for fast, balanced everyday answers.
  • A second vendor, such as Claude or Grok, to compare answers.
NewKnowledge

Private knowledge documents

New documents start private. Share each one with people or teams.

Knowledge documents give AI jobs and chat the facts they must follow, such as a refund policy or a price list. A document you create is private until you share it.

  • Documents you already have stay shared with your organisation.
How it works
  1. Create a document in Library. You start as its only owner.
  2. Click Share and pick a person or a team.
  3. Grant View to read, Edit to change, or Owner to manage access.
  4. Attach it to an AI job, or type @ in chat to add it.
Use it for
  • Keep a draft to yourself until it is ready.
  • Let one team edit a policy that others only read.
  • Give AI jobs the rules they have to follow.
NewIntegrations

Mailgun delivery events

Mailgun reports each delivery, bounce, complaint, and unsubscribe as an event.

  • Soft and hard bounces arrive as separate events.
  • Omnivery shows a rejected delivery callback and how to fix it.
NewIntegrations

Edit GitHub releases

Change the title or notes of a published release.

ImprovedBuilder

Workflow edits stay in scope

Ask for one change and get that one change.

  • Many failed edits recover before you have to retry.
  • Chat history comes back after a page reload.
  • Chat and Builder stay on the same branch and version.

In the oven

Early access. Ask, and we switch it on for your workspace.

Early accessData

Databases, built in

Create a Postgres database in your workspace. Browse and edit it in Library.

A database gives your workflows a place to keep structured data, such as orders or leads. Each one is a Postgres database that sits in Library next to your workflows and documents.

How it works
  1. Ask OAIZ to create a database and its tables for you.
  2. Open it in Library to browse, filter, and edit rows.
  3. Run your own SQL from the Query tab.
  4. Mention the database in chat with @ to ask about its rows.
  5. Let jobs read and write rows as a workflow runs.
Use it for
  • Track orders, leads, or tickets that workflows update.
  • Keep a record of what each run did.
  • Answer chat questions with your own data.
Ask for access
Early accessDataAI models

Query with AI

Describe the rows you want. OAIZ writes the SQL and runs it.

Query with AI turns a plain question into SQL for one of your databases. It reads the tables first, writes a single statement, and runs it, so you get rows instead of syntax.

  • Writes still ask before they run.
  • Members with view access get read queries only.
How it works
  1. Open the query page of any database.
  2. Type the question in the editor in plain words.
  3. Click Query with AI. The SQL replaces your text and runs.
  4. Adjust the SQL by hand and run it again if needed.
Use it for
  • Answer a sales question without writing SQL.
  • Check the data before a workflow depends on it.
  • Learn SQL by reading the statements it writes.
Ask for access
Early accessIntegrations

Outlook mail

Send, reply to, and forward Outlook mail. Start a workflow when mail arrives.

  • Search, read, move, and delete messages.
  • Set categories and follow-up flags.
  • Drafts keep their inline images.
Ask for access
Early accessIntegrations

Google Docs, Sheets, Slides, and Drive

Write Docs, fill Sheets, and build Slides decks. Search and organise Drive files.

  • Create spreadsheets, then read, write, and append rows.
  • Comment on Docs and suggest edits.
  • Fill a Slides template in one step.
  • Upload and download Drive files.
Ask for access
Early accessIntegrationsBuilder

Custom API actions in workflows

Use a saved action from your own API integration as a step in any workflow.

Custom API actions connect workflows to an HTTP API that has no ready-made integration, such as an internal CRM. Save a call once on a custom integration, then reuse it in any job.

How it works
  1. Add your API as a custom integration with a base URL and credential.
  2. Save each call as an action with its inputs and response schema.
  3. In the job builder, pick the action under the integration name.
  4. Map its inputs from the event. The response becomes the job output.
Use it for
  • Create a contact in your CRM when someone signs up.
  • Look up an order in an internal system.
  • Call a partner API with one shared credential.
Ask for access

Improvements and fixes

  • Improved

    Billing in your currency. Usage, logs, and the builder show costs in the currency you pay in.

  • Improved

    Gmail checks the sender first. Sends and drafts from an unverified Gmail address stop before they go out.

  • Improved

    Logs stay out of the way. After a run, logs stay collapsed and the preview opens at a third of the screen.

  • Improved

    Load more in Library. Folders add items to the list as you load more, instead of switching pages.

  • Fixed

    Discarded edits stay gone. After you discard an edit, the AI no longer builds on it.

  • Fixed

    Firecrawl errors. Timeouts and missing pages say what to try next.

  • Fixed

    Slack names. Canvas previews show Slack channel and user names instead of IDs. Enrich skips archived channels.

  • Fixed

    Names in old logs. Execution logs keep workflow and job names after you delete them.