Hub Flow & ATZ
Hub Flow is HUB iABOT's conversational and logic engine. It turns your AppWebs into living systems that understand context, reply over WhatsApp or Telegram, and share the same database — without writing handlers or orchestrating tools separately.
What is an ATZ?
An ATZ (Automation) is a visual flow of nodes: a diagram that dictates how your assistant should respond to every interaction. Instead of coding backend controllers, you describe the logic and Hub assembles it for you.
1. Describe
Express your intent via text or voice in the HUB Flow Assistant.
2. Generate
The Builder Agent understands your logic and assembles the nodes automatically.
3. Deploy
Clicking "Create ATZ in Flow" makes the diagram ready for your channels.
The node canvas
The Flow engine is agnostic and data-driven. There are no fixed vertical nodes, only generic building blocks that bring any process to life:
| Category | Main nodes |
|---|---|
| Input and Logic | input, menu, button |
| Data | list_records, create_record, update_record, status_updater |
| AI Actions | ai_action |
| Output and Channels | notification, telegram, whatsapp |
Builder Agent
The Builder Agent takes your natural language instruction and turns it into functional nodes — menus, conditions, AI actions, and database reads and writes.
- Complex nodes: Deep logic is resolved by DeepSeek V4 Pro/Flash.
- Fast structure: Quick assembly is delegated to ultra-fast models via Groq.
From Studio to Flow
Building the AppWeb and the conversational automation happen within the same ecosystem. From the visual Hub Studio environment, the HUB Flow Assistant reads the context of your generated site and lets you define the bot's intent.
Clicking the "Create ATZ in Flow" button transfers that intent to the Builder Agent and deploys it instantly.
The bridge between UI and Backend
Hub Flow is what lets a button clicked in your AppWeb trigger a change in your database, and that same database update trigger a notification in the customer's conversational assistant. The data cycle closes completely and transparently.
See how to connect Flow in the tutorial
Native Omnichannel
Your AppWeb doesn't live in isolation. Once connected to Hub Flow, the conversational assistant can be exposed on multiple channels simultaneously while keeping a shared state.
Implicit Voice
On WhatsApp and Telegram, you don't need to configure voice recognition nodes. If a user sends a voice note, Hub automatically transcribes it with Groq Whisper before it reaches your flow. Your ATZ always works with text.
Resources in Flow
Certain multimodal resources are exclusive to Flow ("Flow Only"). For example, channel integrations, or the ability to process documents with OCR by sending a photo within the conversation.
Generation Costs
The Builder Agent and Copilot debit Hub AI Credit (your single account balance). Your plan includes credit; you can top up when needed.