INTERACTIVE FIELD GUIDE
Which task would you start with?
Explore five recipe patterns, then follow the matching guide below for the complete example and setup.
Give a visitor a useful next step
The FAQ starter offers opening hours, delivery information, and a path for other questions.
- 01New conversation
- 02Ask a three-choice question
- 03Follow the selected branch
- 04Send the configured reply
What you configure
Replace the sample hours, delivery policy, public links, and next-step wording. Assign the workflow to a test Line.
Check before launch
Try each choice in a fresh conversation and confirm every reply. This starter uses fixed messages and has no AI processing.
Summary of the simple FAQ recipe. The three answers are alternative branches; they do not run one after another.
Move the visitor’s words to the service desk
Receive the customer’s text and submit it to a configured intake endpoint.
- 01Ask for the request
- 02Receive the next text message
- 03POST to the intake endpoint
- 04Acknowledge or give a fallback
What you configure
Set your real intake URL and authorization. The starter sends text/plain; adapt the mapping if your service expects another format.
Check before launch
Confirm the request arrives once, test quotes and line breaks, and try an unavailable endpoint. Submission does not mean a team member has read it.
Summary of the website service request recipe. Success and failure take separate reply branches.
Understand the CRM result before adding a write
Start manually with a known test email and inspect what the CRM returns.
- 01Run manually
- 02Search CRM by test email
- 03Keep the lookup result
- 04Inspect in Workflow Activity
What you configure
Choose the search endpoint, authorization, email parameter, and a controlled test contact.
Check before launch
Test a match, a non-match, and an API failure. Review pagination. This starter does not create or update contacts.
Summary of the CRM contact lookup recipe. A failed request records a separate failure result.
Retrieve the pipeline data before the meeting
Use a daily schedule to make CRM pipeline data available to the next reporting step.
- 01Cron starts the workflow
- 02Request pipeline data
- 03Keep the report output
- 04Review before adding delivery
What you configure
Set the schedule and timezone, reporting API, authorization, date range, and deal stages.
Check before launch
Compare the result with the CRM’s own report. Add and test a delivery action separately; the supplied starter does not send the report.
Summary of the daily pipeline recipe. Failure records an unavailable-report result rather than a successful report.
Ask the right question for each service
Give haircut, color, and spa requests their own conversation branches.
- 01New conversation
- 02Choose the service
- 03Ask and receive details
- 04Acknowledge the request
What you configure
Replace the service menu, branch questions, and follow-up wording. Use a team-supported test Line so requests can be reviewed in Inbox.
Check before launch
Test every service branch. The starter collects an inquiry; add reviewed Calendar availability and event creation to confirm bookings.
Summary of the salon and spa intake recipe. The starter does not create calendar events.
A visitor asks whether you deliver to their area. A colleague checks whether a contact already exists in the CRM. Someone gathers the same pipeline figures before the morning meeting. Each task is familiar enough to explain. Turning it into a workflow can still leave you wondering where to begin.
The Chatigram recipe library gives you a starting point you can inspect. Open a guide, follow its diagram, look inside the nodes, and see which values belong to the example and which need to come from your business. Importable starters include workflow JSON you can copy into Chatigram.
Choose a task you recognize from the five examples below. The interactive guide above summarizes the paths; the linked documentation contains the full setup and copyable definition.
1. Give recurring questions a clear answer
“What are your opening hours?” is a good first workflow because you already know what a correct answer looks like. The simple FAQ assistant recipe offers three choices: opening hours, delivery, and something else. Each choice leads to a message you control.
The flow: New conversation → ask a multiple-choice question → send the reply for the selected option.
Replace the example hours and delivery wording with your own information. Use a current public link when a policy needs more detail, and give the “Something else” branch a useful next step. Try every option in a fresh test conversation.
This starter uses a menu with fixed replies. If customers need to ask free-form questions, the guide explains how to extend it with Receive Message and a suitable AI action. You can learn the branching pattern first, then add the AI connection and business context when the task calls for them.
2. Turn a website message into a service request
Imagine a repair business whose website visitors describe a problem in chat. The team wants that description to reach the service desk where requests are handled. The website service request recipe connects those two moments.
The flow: New conversation → ask what the visitor needs → receive their text → submit it to the intake endpoint → acknowledge success or explain the fallback.
Configure the actual intake URL and its authorization. The starter sends the received message as plain text, so check what your service desk accepts. If it expects a structured request, adapt the input mapping to its API.
Then send a test message with quotes and line breaks and look for the request at the destination. Try an unavailable endpoint too. The success reply should mean the request was submitted; your team’s response time is a separate part of the service you provide.
3. Look up a CRM contact before adding another
A returning customer may use the same email address in several conversations. Before extending a workflow to create another contact, make sure you understand how the CRM finds an existing one. The CRM contact lookup recipe is a small, deliberate way to learn that response.
The flow: Manual run → search your CRM using a test email → keep the returned result, or record a lookup failure.
Select a known test contact, configure your CRM’s search URL and access, and inspect the output in Workflow Activity. Does the API return an exact email match, several possible contacts, or a page of results? Repeat with an email you know is absent.
The supplied workflow performs the lookup only. Once that works, you can design the decision around creating or updating a contact. Keep an empty result and a failed search as distinct outcomes; a service outage should not become a reason to create duplicates.
4. Have the pipeline data ready before the meeting
For a sales coordinator, the useful result may be a consistent view of open deals before the team meets. The daily CRM pipeline report recipe shows how a schedule can retrieve that information and pass it to a reporting step.
The flow: Daily Cron trigger → request pipeline data → keep the response for reporting, or record a failure.
Review the sample 09:00 UTC schedule and set the timezone that defines your team’s working day. Configure the CRM endpoint, deal stages, and reporting period, then compare the result with the CRM’s own report using the same filters.
The starter stops with the report output available. Add formatting and a delivery action when you know what colleagues need to see. A short message with a link back to the CRM might be more useful than forwarding the entire response. Our guide to scheduled business workflows explores how to choose the timing around the decision someone needs to make.
5. Make a booking inquiry easier to follow
A haircut, a color appointment, and a spa treatment need different questions and different amounts of time. The salon and spa recipe starts by giving each service its own conversation branch.
The starter flow: New conversation → choose a service → ask for the relevant details → receive the reply → acknowledge the request.
Edit the choices and questions to fit your services. The initial workflow collects the inquiry for your team to review in Inbox. It does not create a calendar booking.
When you are ready to add booking, follow the appointment guide to configure Google Calendar availability and event creation. Choose the correct calendar, service duration, business hours, and resource. Send a booking confirmation only after the event is created; an unavailable slot needs another choice. The library also includes gym and studio and appointment change guides.
Take one recipe from the diagram into your workspace
Start with the guide closest to your task. Read the diagram’s branches and expand the node configuration before copying. For importable starters, use Copy workflow JSON or download the definition, then choose Paste/Import Workflow while creating a workflow in Chatigram.
Replace the example information and configure your own connections. API examples deliberately use non-working placeholder URLs. Keep the setup disabled while you prepare it, then run a controlled test and check both Workflow Activity and the destination. A successful import tells you the definition was accepted; the test shows what actually happened.
If your task is managing a community or preparing email, the library also covers the official Telegram Group Manager and Multi Email Sender setups. Those guides follow the in-app template wizards, so use their setup steps.
Open the recipe library, choose one useful outcome, and follow it through. Once you can explain each step and verify the result, you have a workflow you can make your own.
