The building blocks
Understand organizations, Lines, workflows, nodes, branches, variables, and connections without needing a technical background.
- TRIGGERAn event happens
- STEP 01A node does the work
- STEP 02A branch chooses the next step
Start with a real task #
Imagine a customer asks about an order. You want to collect the order number, look it up, and send a helpful answer. Each part has a place in Chatigram.
| Building block | What it means | Order support example |
|---|---|---|
| Organization | The workspace containing your team and resources | Your support team’s workspace |
| Line | A customer conversation channel | Your website’s Live Chat |
| Workflow | The instructions for an automated task | An order support assistant |
| Trigger | The event that starts a workflow | A new conversation begins |
| Node | One step of work | Ask for the order number |
| Variable | A value you can use in later steps | The customer’s order number |
| Branch | A possible path through the workflow | Order found or not found |
| App Connection | An authorized account for an external service | Your store account |
| Inbox | The place to read and reply to conversations | An agent follows up |
Lines and connections do different jobs #
A Line receives and sends customer conversations in a channel. An App Connection lets workflow actions access another service. A Telegram Line and a Telegram action connection can both exist, but creating one does not automatically configure the other.
The currently implemented Line types are Live Chat, Telegram, and WhatsApp. The node catalog includes other messaging and social actions; those actions do not mean every service also appears as an Inbox Line.
With Private AI mode enabled on a Line, its conversations are hidden from Inbox and human agents cannot view or reply. Use a team-supported Line when your process requires Inbox follow-up or a human handoff.
Triggers start; nodes continue #
Every ordinary workflow has one trigger. After the trigger, a node can send a message, receive an answer, make a decision, update a record, call an app, or process data with AI.
Some workflows serve conversations. Others run manually, on a schedule, after a database operation, or when an HTTP request arrives. Choose a trigger that supplies the context your later nodes need.
Values move through variables #
The output of one step becomes the input of another. Use the variable picker to select a value from the trigger, a workflow Property, or a previous node. You do not need to invent reference syntax.
For example, a Receive Message step can provide a text answer. A later message can include that answer through the variable picker. If the source node never runs, the value may be empty.
Save a change, then observe a run #
The editor describes the workflow. Workflow Activity shows what happens when it runs. A workflow may wait for a customer response; waiting can be expected behavior. Saving a change does not undo actions that a previous run already performed.
Continue with the editor or choosing a trigger.