Chatigram documentation

Build assistants, automate workflows, and connect channels with Chatigram.

1. Getting started

Chatigram lets you build AI-powered assistants that run on chat channels like Livechat, Telegram, WhatsApp, Instagram, and more. You design the logic visually, and Chatigram handles routing, AI calls, and messaging for you.

  • Create Lines for each channel (website widget, Telegram, etc.).
  • Design Workflows in a visual editor using nodes.
  • Use Ask AI nodes for intelligent responses.
  • Monitor and intervene from the Inbox.
Quick start: Create a Line (e.g. Livechat) → Create or duplicate a workflow → Attach it to the Line → Open the direct chat link to test the full flow.
Tip – You don’t need to be a developer to start. Most use cases can be built visually using nodes for messages, conditions, and integrations.
Where to use Chatigram: Your account is available at app.chatigram.com. This documentation will continue to evolve as we release new features like Chatigram Page and native mobile apps.

1.1 Sign up & sign in

You can sign up or sign in to Chatigram using:

  • SSO providers: Google, Microsoft, LinkedIn, Facebook.
  • Email: create an account or log in using your email address.

Chatigram supports installation as a Progressive Web App (PWA) in modern browsers, so you can “install” it and open it as if it were a native desktop app.

2. Core concepts

2.1 Lines

A Line is a communication channel where conversations happen. Examples:

Livechat (website widget) Telegram WhatsApp Instagram …etc.

2.2 Workflows

A Workflow is a visual automation made of connected nodes. It defines how Chatigram responds to:

  • New conversations and messages.
  • Changes in conversation status.
  • Incoming webhooks.
  • Scheduled time-based events (cron).

2.3 Nodes

Nodes are the steps in a workflow. Examples:

  • Send Text Message – reply to the user.
  • Receive Text Message – wait for user input.
  • Ask AI – send a prompt to a configured AI model.
  • External API integration – call HTTP APIs and extract data.
  • Check Condition – branch logic based on rules.
  • Set Variable – store values for later use.

2.4 Variables

Variables store data such as user replies, workflow properties, AI responses, and API results. You insert variables into node fields using the variables picker.

2.5 Inbox

The Inbox shows all active and historical conversations. You see both user messages and actions taken by workflows. You can always step in and reply manually.

3. Lines & channels

3.1 Viewing lines

Open the Lines page to see all configured channels. For each line you’ll see:

  • Name – e.g., “Default”, “Chatigram Website”.
  • Type – Livechat, Telegram, WhatsApp, Instagram, etc.
  • Status – connected or not.

3.2 Creating a new line

  1. Navigate to Lines.
  2. Click Create new.
  3. Select the channel type (e.g. Livechat or Telegram).

Then configure:

  • Line name – an internal label.
  • Allowed workflows:
    • All – any enabled workflow can run on this line.
    • Some – choose specific workflows to handle chats.
    • None – no workflows; only manual handling.
  • Appearance (Livechat) – chat title, subtitle, logo, brand color.
  • Embedding (Livechat) – website URL, tooltip text, and script snippet.

3.3 Direct chat links

Each Livechat line provides a Start a new chat link. Use this link to:

  • Test the workflow quickly in your browser.
  • Share a direct chat experience with users.

3.4 Embedding the Livechat widget

You’ll see a snippet similar to:

<script type="module" src="https://app.chatigram.com/livechat/web-js-sdk.js?token=YOUR_TOKEN"></script>

Paste it in your website’s <head> section. The widget will appear using the appearance defined for this line.

4. Inbox

4.1 Conversation list

The left side of the Inbox shows:

  • All conversations for your organization.
  • Last message preview.
  • Status (Pending, In Progress, Closed, etc.).
  • Line/channel information.

4.2 Conversation view

Clicking a conversation opens the full message history:

  • User messages.
  • Workflow messages (marked as “Workflow”).
  • Status updates.

4.3 Filters

You can filter chats by:

  • Line / channel type.
  • Status.

4.4 Manual replies

Use the message box at the bottom to manually respond to the user, even if workflow automation is active. This is ideal for escalations or edge cases.

5. Conversation statuses

5.1 Defaults

Common default statuses include:

  • Pending
  • In Progress
  • Closed

5.2 Managing statuses

  1. Go to Settings → Conversation statuses.
  2. Create new statuses, rename or recolor existing ones.
  3. Set a default status for new chats.

5.3 Updating status via workflows

Use the Update Conversation Status node to change the status automatically as the workflow progresses (e.g. mark as Closed after a final message).

6. Billing & plans

Under Manage billing you can review your current plan and limits. Plans vary by:

  • Number of active lines.
  • Number of enabled workflows.
  • Other feature or usage differences.

You can adjust plans as your organization grows or your automation needs change.

7. Organization

7.1 Organization structure

In Chatigram, every user can create one organization of their own, but they can join multiple organizations as either an Admin or a Member.

  • Admin:
    • Full access to organization settings.
    • Can manage lines, workflows, billing, and members.
    • Can view and manage all conversations.
  • Member:
    • Focused on support and communication.
    • Access to the Inbox and assigned conversations.
    • Ideal for support agents and operators.

7.2 Organization settings

The Organization area allows you to manage:

  • General workspace profile (name, branding).
  • Members and roles.
  • Billing ownership and visibility.

7.3 Leaving an organization

From the General tab, you can choose Leave organization, which removes your access to that workspace. You can still participate in other organizations you are part of.

8. Workflows overview

Workflows define how Chatigram reacts to triggers and how it moves through different steps and decision points.

  • Each workflow has one trigger.
  • Workflows consist of nodes connected in sequence or branches.
  • They use variables and workflow properties as data.

8.1 Creating workflows

You can create workflows in three ways:

  1. Blank workflow
    Choose a trigger and build the flow step-by-step in the editor.
  2. Official Templates
    Start from pre-built workflows such as:
    • Business Connect Agent – ideal for websites, help desks, internal tools, or client-facing platforms.
    • Profile Connect Agent – perfect for freelancers, creators, consultants, and professionals who want to stay responsive without being online all the time.
    New templates are being added over time, so you can quickly launch common patterns without designing every node from scratch.
  3. Copy Existing Workflow Duplicate
    Duplicate an existing workflow from the list, then rename and adjust it. This is ideal when creating variants for new languages, brands, or slightly different flows.

8.2 Workflow editor

The workflow editor is a visual canvas. At the top you typically see a trigger node, followed by message, AI, condition, and integration nodes.

  • Click any node to edit it in the right sidebar.
  • Use the + connector below a node to attach the next step.
  • Use branching nodes like Check Condition and Ask multiple choice to split logic.

9. Workflow properties

Workflow properties are global fields configured in the workflow editor sidebar under Properties. They:

  • Are not shown directly to users.
  • Act as training content for AI or reusable text blocks.

9.1 Properties from official templates

Official templates often define example properties such as:

  • About (for AI Training)
  • Services & Products (for AI Training)
  • FAQ (for AI Training)
  • How to connect
  • Ask for name

You can freely edit or remove these, or add new custom properties for your use case.

9.2 Creating custom properties

  1. Open the workflow in the editor.
  2. In the sidebar, open the Properties section.
  3. Click Add property.
  4. Fill in:
    • Label – display name (e.g. “Company mission (AI Training)”).
    • Info – short description for editors.
    • Value – the content itself.
    • Required – if it must be filled.

9.3 Using properties with AI

In an Ask AI node, use the variables picker to insert properties into the System content. This gives the AI background knowledge about your business while keeping your prompts short and maintainable.

10. Variables

Variables store data for a single workflow run. They can come from:

  • User input (Receive text, Multiple choice answers).
  • Node outputs (Ask AI, External API, Verify Email, etc.).
  • Workflow properties.
  • Set Variable nodes.

10.1 Using variables

Where a field shows a Variables dropdown, click it to insert any available variable. At runtime, Chatigram replaces the placeholder with the actual value.

10.2 Naming guidelines

  • Use descriptive names like user_name or selected_plan.
  • Avoid generic names like data1 for important variables.
  • Keep naming consistent across workflows.

11. Multi-language support

With Automatic translations, a single workflow can serve users in many languages.

11.1 Enabling translations

  1. Open your workflow in the editor.
  2. In the sidebar, find Multi-language support.
  3. Enable Automatic translations.
  4. Configure the Language selection message.
  5. Set a Default language and add Other languages.

11.2 User experience

When users start a chat, they will see a language selection question with buttons. Once they choose a language, messages are translated between their language and your default language automatically.

12. Node reference

The following sections summarize primary node types in Chatigram workflows.

12.1 Trigger nodes

  • Conversation Start – runs when a conversation begins.
  • New Chat Created – runs when the first message of a new chat is received.
  • New Text Message – runs when a message matches configured criteria.
  • Chat Status Change – runs when a conversation’s status changes.
  • Webhook – runs when an external system calls a generated URL.
  • Scheduler / Cron – runs based on a time schedule.

12.2 Input nodes

Receive Text Message

Pauses the workflow until the user sends their next message. The message is stored in a variable that you can use later (for AI, APIs, or conditional checks).

12.3 Action nodes

Send Text Message

Sends a chat message to the user. You can combine static text with variables to make personalized responses.

Ask Multiple Choice Question

Displays a question and a set of clickable options. Each option has its own branch so you can route users differently depending on their choice.

Send Email

Sends an email using your configured email settings:

  • To – a fixed email address or a variable.
  • Subject – supports variables.
  • Body – HTML or plain text with variables.

Verify Email

Validates an email address and optionally sends an OTP. It exposes two branches:

  • Valid – email passes validation.
  • Invalid – email fails validation.

Update Conversation Status

Changes the conversation’s status to any of your configured conversation statuses.

12.4 Control nodes

Set Variable

Assigns a value to a variable. Often used to store user choices, flags, or intermediate values.

Check Condition

Evaluates rules and routes execution to Yes or No branches. Supports:

  • equals / does not equal
  • contains / does not contain
  • begins with / ends with
  • ignore case

You can combine multiple conditions using AND/OR groups for more complex logic.

A/B Testing

Splits the flow randomly into multiple branches so you can experiment with different messages or flows.

12.5 Ask AI node

The Ask AI node sends a prompt to a configured AI model and stores the reply in a variable. The underlying model is configured internally; workflow builders do not choose the model.

Fields:

  • Node name – label shown in the editor.
  • System content – short instruction defining the AI’s role/behavior.
  • User content – the main prompt, usually including variables.
  • Response value name – variable name to store the AI reply.
Internally, Chatigram sends a chat completion request and extracts choices.0.message.content from the provider’s JSON response into the specified variable.

Example:

  • System content: “You are a helpful assistant that answers briefly and clearly.”
  • User content: “Answer the user’s question: {{user_question}}”
  • Response value name: ai_answer

12.6 External API integration node

The External API integration node calls REST APIs and lets you map response data into variables. You can use it to:

  • Call your own AI models or other model providers.
  • Integrate with business systems (CRM, ERP, ticketing tools, internal dashboards).
  • Create or update records in your own backend services.
  • Book appointments (for example with Google Calendar APIs).
  • Trigger actions in SaaS tools (e.g. marketing platforms, payment systems).
  • Method – GET, POST, PUT, DELETE, PATCH, etc.
  • URL – endpoint, supports variables.
  • Headers – e.g. Content-Type: application/json, Authorization.
  • Query parameters – appended to the URL as query string.
  • Request body – usually JSON, supports variables.

Response extraction

  • Get whole response – store entire body as text.
  • Extract JSON value – use JSONPath to extract a field.

Examples:

  • choices.0.message.content – first AI message content.
  • data.user.name – a name field inside nested JSON.

13. External API integration – example

Goal: Fetch a user’s profile from an external API and greet them.

  1. Add an External API integration node.
  2. Method: GET.
  3. URL: https://api.example.com/users/{{user_id}}.
  4. Headers: add any required auth headers (e.g. Authorization).
  5. Add a JSON value extractor:
    • Variable name: user_name
    • JSONPath: data.name
  6. Connect a Send Text Message node:
    • Message: “Hi {{user_name}}, welcome back! How can I help you today?”

You can use the same pattern to:

  • Create a booking by calling a Google Calendar API endpoint.
  • Push leads into your CRM when a user shares contact details.
  • Start a workflow in your internal systems whenever a chat reaches a specific step.

14. Example workflows

14.1 Simple greeting assistant

  1. Trigger: Conversation Start.
  2. Node: Send Text Message – “Hi! How can I help you today?”

14.2 Multi-language welcome assistant

  1. Enable Automatic translations in the workflow settings.
  2. Trigger: New Chat Created.
  3. Ask Multiple Choice: “What do you need help with?” (e.g. “Pricing”, “Support”, “Other”).
  4. Route each choice to separate branches or Ask AI nodes.

14.3 FAQ assistant using Ask AI + properties

  1. Start from an official FAQ-style template or add properties:
    • About (for AI Training)
    • Services & Products
    • FAQ
  2. Trigger: New Text Message.
  3. Ask AI:
    • System content: include About/Services/FAQ properties via variables.
    • User content: user’s message variable.
    • Response variable: ai_answer.
  4. Send Text Message: “{{ai_answer}}”.

14.4 Duplicate and customize a workflow

  1. Open the Workflows page and find a workflow that already works well.
  2. Use the Copy / Duplicate action.
  3. Rename the copy (e.g. “Profile Assistant – ES”).
  4. Update:
    • Workflow properties (About, FAQ, etc.).
    • Language settings.
    • Nodes/messages for the new variation.

15. Troubleshooting

15.1 Workflow doesn’t trigger

  • Check that the workflow is Enabled in the editor sidebar.
  • Ensure the trigger type matches your scenario (message vs. status vs. webhook).
  • Confirm that the workflow is allowed on the Line (Lines → Allowed workflows).

15.2 Variables are empty

  • Verify that the node responsible for the variable executed before it’s used.
  • Check JSONPath expressions in External API nodes.
  • Ensure variable names are spelled correctly everywhere.

15.3 External API errors

  • Double-check endpoint URLs and HTTP methods.
  • Verify headers (Authorization, Content-Type) and body format.
  • Use node logs to inspect error messages returned by the API.

15.4 AI node issues

  • Ensure both System content and User content are set.
  • Keep system instructions concise and clear.
  • Constrain answer length when needed (e.g. “Answer in 3 bullet points”).

15.5 Widget not loading

  • Make sure the script is in your site’s <head>.
  • Confirm the line is connected and active.
  • Check the browser console for JavaScript errors.

16. Glossary

  • Line – a communication channel (Livechat, Telegram, WhatsApp, Instagram, etc.).
  • Workflow – a visual automation built from nodes.
  • Node – a single step in a workflow.
  • Trigger – an event that starts a workflow.
  • Workflow property – global field used as configuration or AI training content.
  • Variable – a runtime value used within a workflow.
  • JSONPath – syntax for extracting values from JSON responses.
  • A/B Testing – randomly splitting traffic into multiple branches.