Key concepts
Glossary of the core elements of Pulbot. Reading this once saves confusion when building flows.
Reference
- Flow
- A complete automation: a set of connected nodes that execute in sequence when an event arrives (message, webhook, etc.).
- Node
- A step inside a flow. Each node executes exactly one tool with the configuration you assign.
- Tool
- A reusable piece of logic. Can be an API call, data transformation, if/else condition, AI agent, or custom code.
- Trigger
- Special start node. Listens for events from a channel (incoming message, callback, webhook) and starts the flow.
- Transition
- Arrow connecting two nodes. Defines which node runs after which, and under what condition (always, on success, on error).
- Connector
- Credentials stored securely for an external service (WhatsApp, OpenAI, HTTP Basic, etc.). Nodes reference the connector, not the secret directly.
- Channel
- A messaging account connected to Pulbot: a WhatsApp number, Telegram bot, or Instagram account. A flow runs on a specific channel.
- Variable
- Data that travels through the flow. Declared in the trigger or generated in a node. Referenced as {{variableName}} in downstream node configs.
- Inbox
- CRM inbox where you see all active conversations across all channels. Lets you reply manually, view history, and tag contacts.
- KV Store
- Session key-value store. Saves data between executions for the same user (e.g. funnel step, session token).
- Knowledge Base (KB)
- Files (PDF, txt) that the AI agent can query to answer questions based on your content.
- Run
- Each execution of a flow from the trigger to the last node. Pulbot charges $0.005 per production run.
- MCP
- Protocol that lets Claude (or another external agent) build and manage Pulbot flows directly from code or terminal.
Next step
Connect your first channel: WhatsApp, Telegram, or Instagram.