Using AI nodes
Translate copy and generate imagery or video inside a flow, with your own provider keys.
The AI Node runs an AI task as part of a flow: translating copy per market, transforming text, or generating imagery and video. It uses your organisation's own provider keys, so you stay in control of models and spend.
Before you start
- AI nodes are part of the Business+ plan.
- An owner must connect at least one provider under Settings > Integrations > AI: see Connecting OpenAI, Connecting Gemini AI Studio or Connecting Anthropic.
- Owners can also cap weekly AI usage and decide which roles may run AI nodes.
Set up an AI Node
- Add an AI Node from the palette's AI group.
- Pick the Task: translating text, generating an image, generating a video. The list shows what your connected providers support.
- Pick the Provider and Model. The model list follows the provider, the task, and any restrictions your organisation has set.
- Pipe the task's inputs in: for translation, the source text rows.
- Market and language settings are pipe-only: connect your Market and Language rows so every pairing is covered. The node flags any pairing the pipes miss.
- Optional settings, depending on the task: a glossary (approved terminology per market), a creativity level, and additional instructions in your own words.
Preview
Use the node's Preview to run a sample without building: one result per pairing, shown on the node. Preview results are kept, so reopening the flow doesn't re-spend.
Building with AI
When you click Build and some AI results aren't cached yet, the build pauses on a warm-up step showing exactly how many provider requests are needed before anything is spent. Confirm to run them; progress appears in a toast and carries on in the background, even if you navigate away or close the tab. Identical requests are cached, so rebuilding an unchanged flow doesn't call the provider again.
Budgets and errors
Owners can set weekly budgets for AI requests, image generations and video generations. When a budget is exhausted, the node says so and the build stops cleanly. Provider problems (an invalid key, a rate limit) surface on the node's label with the reason.