Add an authenticator app, a passkey, or a security key as a second step at sign-in.
With a second factor, a password alone does not open your account. After the password, OAIZ asks for a code from your authenticator app or for your passkey or security key.
Administrators require a second factor for everyone, or for administrators only.
Recovery codes sign you in if you lose your authenticator app.
Administrators reset a member’s second factors from the Users tab.
How it works
1Open Account Settings from the menu under your name, then the Security tab.
2Click Set up next to Authenticator app and enter your password.
3Scan the QR code, type the 6-digit code, and save your recovery codes.
4Click Add passkey or security key to register your device as well.
5Sign out and in again. After your password, enter the code or use the passkey.
Use it for
Stop a leaked password from opening your workflows.
Confirm sign-in with a fingerprint or a hardware key.
Follow a company policy that asks for two-factor sign-in.
NewBuilder
Tag any earlier property
Released on 4 Oct 2026
Pick a property from any earlier job or the trigger event. Saving passes it along for you.
A job often needs a value that an earlier job made, such as a customer ID from two steps back. The property picker lists every property your job can reach, with the job it came from, and saving forwards it through the jobs in between.
Output properties and conditions offer the same list.
A save that cannot forward a property says so.
How it works
1Open a later job of a workflow in the Job Builder.
2Type @ in the prompt or in an input to list available properties.
3Pick a property. Each one names its source job or the trigger event.
4Save. OAIZ passes the property through every job in between.
Use it for
Put the sender’s email from the trigger into a reply three jobs later.
Use an order ID from the first job in a final report.
Filter a late step on a score an early job gave.
NewBuilderIntegrations
PDF attachments from code jobs
Released on 4 Oct 2026
A Code job builds a PDF. The next Gmail job sends it as an attachment.
Some workflows end with a document, such as an invoice, a quote, or a weekly report. A Code job writes the PDF and stores it with the run, so a Gmail job after it attaches the file to the email.
A job that requires a file fails without one, before any email.
How it works
1Ask OAIZ for a workflow that makes a PDF and emails it.
2The Code job builds the file and returns it on its output event.
3The Gmail job after it attaches the files from that event.
4After a run, open or download the PDF under Files in the output event.
Use it for
Email a quote as a PDF when a deal reaches a stage.
Send a weekly sales report to your manager.
Attach a filled-in form to a confirmation email.
NewAI modelsBuilder
Reasoning effort per job
Released on 4 Oct 2026
Choose how much the model reasons in each Agent or LLM Call job.
Reasoning effort sets how long a model thinks before it answers. High effort suits hard judgement calls, and low effort suits quick, cheap steps. The levels on offer follow the model you pick.
Only a person picks the level. AI edits never set one.
How it works
1Open an Agent or LLM Call job and click Model & prompt settings.
2Find Reasoning effort in the Model & prompt dialog.
3Pick a level from None to Max, or keep OAIZ default.
4Save the job. Each run uses that level.
Use it for
Give a contract review step high effort.
Keep a simple tagging step on low effort to cut cost.
Compare answers at two levels on the same test event.
NewAI models
GPT-6.1 Sol
Released on 4 Oct 2026
Pick GPT-6.1 Sol in chat and in every AI job.
GPT-6 Luna takes the place of Gemini 3.8 Flash in recommendations.
Agent and LLM Call jobs you add start on GPT-6 Luna.
Gemini 3.8 Flash stays selectable by name.
NewBilling
Invoice email
Released on 4 Oct 2026
Send every invoice PDF to one address that an administrator sets in Billing.
Renewal and extra usage invoices arrive as PDF attachments.
Payment history shows each email’s status, with Send again.
Until you set one, invoices go to your subscription email.
ImprovedBilling
Usage follows workflow access
Released on 4 Oct 2026
Members see their own usage and the usage of workflows they can open.
Workflow Owners set spend limits on their own workflows.
Only organisation administrators see the Billing tab.
Spend limits also apply to builder edits and Query with AI.
ImprovedSecurity
Remove members and service accounts
Released on 4 Oct 2026
Remove a member and choose who takes over each workflow, document, and integration they owned.
Delete a service account you manage, and its keys stop working.
Filter Users by people, service accounts, or job accounts.
The Share picker filters by people, teams, organisation, or service accounts.
Search the Share picker by email as well as by name.
ImprovedChat and voiceIntegrations
Integration tools in chat
Released on 4 Oct 2026
Chat names the connected actions that need an access request before you use them.
One integration action returns up to 10 files to the chat.
A timed-out request that changes data is not sent again.
Live voice tells you when a question waits on screen.
Access request cards and the integrations table show provider logos.
ImprovedIntegrations
Slack replies in the thread
Released on 4 Oct 2026
Workflows OAIZ builds to answer a Slack message reply in its thread, unless you ask otherwise.
Channel lists follow every page, as far as 10,000 channels.
Message triggers OAIZ builds skip its own posts.
Adding a reaction that is already there counts as done.
ImprovedBuilder
Edits report what changed
Released on 4 Oct 2026
An edit that changes nothing says so and saves no version.
Code job edits keep their stored tests.
In the oven
Early access. Ask, and we switch it on for your workspace.
Early accessIntegrationsBuilder
MCP tools as workflow steps
Released on 4 Oct 2026
Connect an MCP server, import its tools as saved actions, and run them in any workflow.
An MCP server offers tools from another product, for example a ticket system or an internal API. Add the server as a custom integration and OAIZ imports its tools, so each one becomes a saved action that jobs call.
Failed runs explain the cause and the fix step in workflow logs.
Older Streamable HTTP servers work, and settings show the version.
Start a workflow when a row is inserted, updated, or deleted in one of your databases.
Every committed change to a database row becomes an event that carries the row. A workflow listens for those events, so an order you add or a status you change starts the next job.
Delete a database from Library and restore it within 30 days.
Up to four requests run at once on one database.
Create, migrate, and query databases from the CLI.
How it works
1Tell OAIZ which table to watch and what happens when a row changes.
2Filter the trigger on the table, so other tables do not start it.
3Add or change a row from Library, chat, or another workflow.
4The workflow runs with the row, plus the old row for updates and deletes.
Use it for
Send a welcome email when a customer row is added.
Alert a Slack channel when an order status changes.