INTERACTIVE FIELD GUIDE
Explore the platform by outcome
Switch between three system designs to understand which building blocks do which job.
Connect a conversation to useful context
Keep your existing website and add a connected conversational experience.
- 01Website Livechat Line
- 02Conversation workflow
- 03Business context + AI
- 04Unified inbox
What you configure
Line appearance and embedding, allowed workflows, and the information the assistant can use.
Check before launch
Check mobile behavior, unknown questions, and the path for a visitor who needs a human response.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
Give your application an automation endpoint
Let your application supply an event and the context needed to process it.
- 01App HTTP request
- 02Endpoint-triggered flow
- 03Database or app action
- 04Return or send result
What you configure
Request format, credentials, API nodes, record fields, and the expected completion response.
Check before launch
Validate incoming data and test external API errors. Avoid treating an accepted request as a completed action.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
Share logic across related workflows
A common operation can be packaged as a Node Type rather than rebuilt for every workflow.
- 01Define reusable logic
- 02Create a Node Type
- 03Use in workflows
- 04Maintain centrally
What you configure
The node’s inputs, outputs, behavior, and the workflows that depend on it.
Check before launch
Test changes with representative inputs before relying on them across a shared process.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
Chatigram is easiest to understand as a set of connected building blocks. A workflow describes what happens. A trigger decides when it starts. Lines connect conversational experiences. Apps provide actions and external context. Databases hold structured records. AI can assist inside that system, including while you build it.
Content update: this established article previously included Chatigram Pages. That feature is no longer available. The guide now covers the current platform; its public URL has been retained.
Workflows: the sequence of decisions and actions
A workflow starts with a trigger and connects the steps needed for a result. Chatigram supports conversational triggers alongside webhook, HTTP endpoint, Cron, database operation, and manual starting points. Match the trigger to the event you actually need to handle.
The workflow editor is visual. Chatigram’s editor AI demonstration shows an assistant understanding an existing flow and helping build or update it. Describe your intent, then inspect the generated steps, selected connections, and data passed between them before running the workflow.
Projects: related workflows with shared context
A Project can contain several cooperating workflows. For example, a community may have a conversation assistant, a scheduled summary, and an administration process. Each has a different responsibility while participating in the same wider system.
The Projects post describes enabling, disabling, extending, and combining workflows. That structure helps you change one responsibility without turning the entire process into one oversized flow.
Lines: the connection to a conversation
Lines include website Livechat and supported messaging connections such as Telegram and WhatsApp. You can allow a workflow on multiple Lines. The workflow provides the logic; the Line provides the channel and its settings.
Livechat can be embedded on an existing website. Livechat APIs and webhooks provide a way for applications to build a conversational interface and connect it to workflow logic. Conversations can then be managed in the Unified Multi-Channel Inbox, including human replies when needed.
Apps: the selected accounts behind an action
App connections let workflows work with services such as Gmail, Drive, Docs, Sheets, and supported messaging platforms. The workspace supports multiple connections for supported services, which helps when different tasks need different accounts.
The connected-app example shows a plan, budget, and files created across Google services. For software with an appropriate API, API nodes and incoming HTTP or webhook triggers can connect broader business processes. Configure access and input formats for the particular system.
Databases: structured information inside the platform
Chatigram Databases provide typed fields, visual record management, filtering, sorting, summaries, image handling, REST access, OpenAPI, and database triggers, as described in the Databases demonstration.
A database could hold incoming requests, a content queue, or records used by a workflow. Decide which fields are required and which system owns the authoritative data. A duplicate copy of an external CRM record needs a clear update process.
Node Types: reusable logic you can maintain
Node Types let you package workflow logic as a reusable building block. The Node Types post explains central updates that propagate to the workflows using the node. This is useful when several automations share an operation.
Keep the inputs and outputs well defined. A central change can affect more than one workflow, so test the dependent scenarios rather than checking only the reusable node in isolation.
Templates and Marketplace: useful starting points
Official guided automations include Business Agent, Profile Agent, Multi Email Sender, and Telegram Group Manager. Marketplace publishing supports stores, versioned work, and installable collections, described in the Marketplace post.
Start with the workflow cookbook when you need a concrete task. Explore the workspace when you are ready to configure it. The Free tier gives you a starting point without a credit card.



