AI Assistant overview

The AI Assistant is a docked chat panel that opens from the header on every product page except Settings. Ask it to find media, explain a failed build, tidy the library, draft a whole campaign or generate imagery: it answers with links, clickable thumbnails and cards you can act on. Conversations, unsent drafts and in-flight requests all survive navigating between pages, and even closing the tab: every turn carries on in the background on Nubu's side, so a long job finishes whether or not the page stays open.

Before you start#

• The assistant is part of the Business+ plan.
• An owner must turn on the organisation's AI switches under Settings > Integrations > AI: the master AI enabled switch and the Campaign assistant switch.
• You need the assistant permission; members and admins have it by default.
• At least one AI provider must be connected: see Connecting OpenAI, Connecting Gemini AI Studio or Connecting Anthropic.

Choosing a model#

The model selector reads Auto by default: Nubu picks a suitable model from your connected providers. Each chat can set its own provider, model and thinking level from the selector, and keeps that choice for the whole conversation. Owners can set an organisation default and lock it; locking hides the per-chat provider and model choice, while chats keep their own thinking level.

What it can read#

Reading needs no approval. The assistant can:

• search and inspect assets, opening the actual files to look when names and tags don't settle it, and attaching thumbnails of what it found
• search templates, including which platform placements each composition fits
• read renders and their delivery outcomes, and explain exactly why a build failed
• read glossaries, markets and claims, and run advisory copy checks
• produce workspace reports: renders completed and failed, creatives by status, template usage, storage
• search the web through your own provider key, answering with cited sources

What it changes directly#

Direct changes are limited to additive housekeeping: adding tags to assets and templates, and creating folders. Nothing is renamed, moved, replaced or removed this way.

What it proposes#

Everything else becomes a proposal: creating campaigns and flows, editing flows, renaming, moving or blocking library records, glossary and claim changes, and uploading finished creatives to Meta or Google. Every proposal is a card with Approve and Reject that shows what will change before anything exists. Flow cards are test-built by the same build engine as the real Build, so the card carries the expected creative count, the matrix of what would be produced and any build errors, before you approve anything.

Safety#

The assistant cannot render, publish, spend or delete: those tools do not exist. Everything it uploads to an ad platform arrives paused, for a final human check inside the platform. Approving a card applies exactly the records the card shows: the ids are frozen when the card is offered, so approval can never sweep in records you did not see. And Settings is entirely out of its reach: it cannot read or touch members, billing, plans or API keys.

Costs#

The assistant runs on your organisation's own provider keys at the provider's raw prices (Nubu sells no AI credits), and owners can cap usage with a weekly assistant budget: see Assistant settings and controls.

Next: Prompt examples.