What is Flux
Flux is a visual builder for agentic AI and automation. You drag nodes onto a canvas, wire them together, configure each one with a form, and deploy — no code. The result can be a chatbot on five channels, a scheduled job, an API endpoint, or an autonomous agent that decides for itself which tools to call.
What "agentic" means here
A traditional automation follows a fixed path: this happens, then that happens. An agentic system is given a goal and a set of tools, and works out the path itself. In Flux an AI node can:
- Perceive — read the message, the API response, the spreadsheet row that started the run.
- Reason — decide what the request actually needs.
- Act — call one of the tools you attached to it: hit an API, send an email, look something up, hand the conversation to a human.
- Remember — carry the conversation forward through a memory attachment.
You define the boundaries — which tools exist, what they do, what the agent is for. The agent decides when to use them.
The Flux playground with a workflow of six connected nodes: a WhatsApp trigger, a GPT model node with two tools attached, a decision node and two response nodes
Screenshot to be addedWhat you can build
Multi-channel chatbots
One workflow answering on WhatsApp, Telegram, Viber, Facebook, Instagram and your own website — with the same logic behind all of them.
Autonomous agents
An AI node with tools attached, deciding for itself whether to look something up, email someone, or escalate.
Scheduled jobs
An interval trigger that runs every hour, fetches something, summarises it and posts the result.
API endpoints
An API trigger plus a webhook response turns a whole workflow into an endpoint your own systems can call.
Bulk processing
A spreadsheet trigger walks a file row by row — enrichment, outreach, classification.
Support deflection
A bot that answers from a knowledge base and hands over to a human in Cognify when it cannot.
What is in the box
| Piece | What it gives you |
|---|---|
| 38 nodes | Triggers, actions, AI models, logic, responses, tools and attachments — see the node reference |
| Two model families | OpenAI GPT and Google Gemini, with your own API keys or ours |
| Node Template Language | A small syntax that moves data between nodes without code |
| Credential store | Encrypted API keys, referenced by nodes rather than pasted into them |
| Knowledge base | Attach documents an AI node can answer from |
| Template marketplace | Start from a working workflow instead of an empty canvas |
| Usage analytics | Triggers, tokens, sessions and cost, broken down by provider |
Flux and Cognify
The two products are built to work together, and each is useful alone.
Flux answers
The bot logic, the reasoning, the tool calls, the reply on whichever channel the customer used.
Cognify keeps
The resulting record, its history, the hand-off to a human, and the reporting on all of it.
Flux ships dedicated nodes for that bridge — inbound and outbound chat, chat transfer, table insert and a sheet trigger. See Working with Cognify.
Where to go next
Core concepts is short and everything else assumes it. Then Build your first agent gets something running end to end.