INTERACTIVE FIELD GUIDE
Choose a trigger. See the recipe.
These examples show the shape of a workflow—not a preconfigured template or a promise of an automatic result.
A helpful business assistant
Let a customer ask in their own words, then use your business context to guide the response.
- 01Conversation start
- 02Read configured context
- 03Generate a response
- 04Continue in the inbox
What you configure
A Business Agent, the information it can use, and one or more permitted Lines.
Check before launch
Ask questions that your context does not answer. Make sure the assistant does not invent prices, policies, or availability.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
An event becomes a project brief
An application sends the information a workflow needs to produce a useful document.
- 01Receive webhook
- 02Validate input fields
- 03Create document via app
- 04Save record or notify
What you configure
An event payload, document destination, selected app connection, and required fields.
Check before launch
Test an empty payload and a repeated event. Check sharing permissions on the created document.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
A scheduled content briefing
A recurring task collects information and prepares a draft for review.
- 01Cron schedule
- 02Collect source material
- 03Draft and categorize
- 04Review before publishing
What you configure
The schedule, permitted sources, draft destination, and editorial review process.
Check before launch
Check source links and factual claims. Keep approval in the process when a draft will become public content.
Illustrative workflow idea. Configure the required connections and test it in your workspace; this diagram does not run an automation.
The best first automation is usually a task you already understand. You know its inputs, the decisions people make, and what a useful result looks like. This cookbook gives you six starting points to adapt in Chatigram.
Some capabilities below are shown in published Chatigram demonstrations. The scenarios are workflow ideas: they still need your accounts, context, rules, and testing.
1. Answer recurring service questions
Start with the guided Business Agent setup. Add your business information and connect a Line where customers can ask questions. Test questions about services, hours, and the next step to contact your team. If your context does not contain an answer, the response should acknowledge the gap.
This is useful for a service company that receives similar inquiries every day. The Business Agent post shows the underlying conversational capability. Read how conversations connect to business workflows for the operational follow-up.
2. Create a personal introduction assistant
A Profile Agent can use the personal information, tone, services, and FAQs you configure. Connect it to a Line and let visitors ask about your work. A freelancer could explain their services and collect a project inquiry without treating every visitor as a sales lead.
Chatigram’s Profile Agent demonstration describes this starting point. Review the information you include and avoid exposing private client details in the assistant’s context.
3. Prepare personalized email messages
The Multi Email Sender wizard guides you through connecting an account, configuring the workflow, and testing before launch. The published email demonstration describes personalized messages using Gmail or SMTP.
An example is a set of service updates tailored to known recipients. Verify recipient data, preview the generated text, and send a test to yourself first. Select the correct connection if you have several accounts. This is a configurable workflow, not a reason to send unwanted bulk messages.
4. Turn an application event into documents
An incoming webhook can carry the context for a plan, a budget, or a project brief. Use app connections to create the output where your team works. The Docs, Sheets, and Drive example demonstrates that pattern.
Decide which fields are required before a document is created. A missing deadline should stay missing or trigger a follow-up; it should not become a fabricated date. Test the same event twice so you understand whether it creates duplicate outputs.
5. Prepare scheduled content
A Cron-triggered workflow can collect material, generate a draft, categorize it, and prepare associated imagery. Chatigram’s Halifax.it.com example shows a scheduled content project with generation and publishing steps.
For your own website or social page, begin with draft creation and a review step. Check factual claims, image suitability, source attribution, and the target account before publishing. The schedule saves repeated setup work; editorial judgment still belongs in the process.
6. Manage a Telegram community
The official Telegram Group Manager project combines workflows for group management and advertising. The Telegram automation post describes assistant behavior, moderation, scheduled actions, and group tasks.
Configure the bot, group connection, and intended rules. Enable only the workflows you need and test them in a suitable group before applying them to an active community. Group actions and conversational responses have different consequences, so review both.
Grow from one recipe to a Project
When related tasks need to share context, a Project can organize multiple workflows with separate responsibilities. The Projects explanation describes how workflows can be enabled, disabled, combined, and extended. Keep the steps understandable so you can trace what happened when a result is unexpected.
Explore the platform guide, then open the workspace to try a small workflow on the Free tier. No credit card is required to get started.
