Templates & Facilities

Facilities available around the ChatYug chatbot builders: pre-built flow templates, the Template Message node, keywords, variables, save/publish, testing, and import/export.

Two kinds of “templates”

Concept	What it is	Where
Flow templates	Pre-built chatbot graphs you copy into a new flow (category, description, suggested keywords)	v1: Browse Templates on `/chatbot-flows.html`. v2: Templates button in the builder header
Template Message node	Sends an approved Meta WhatsApp message template (`template_message` node)	v2 palette only — see Nodes Reference

Flow templates (pre-built chatbots)

From the flows list (v1 path)

Open Automation → Chatbot Builder → /chatbot-flows.html.
Use Browse Templates (loads /api/chatbot/flows/templates/list).
Pick a template card (name, category, description, default keywords, usage count).
Enter a flow name; the system creates a new flow from that template with suggested keywords.
Edit nodes, adjust keywords, then save and publish.

From Trial Chatbot Builder V2

Open V2 and click Templates in the header.
Wait for the templates grid to load.
Select a template to apply its structure into the builder, then customize and save.

Flow templates speed up common journeys (support menus, lead capture, FAQs). Always review keywords so they do not conflict with Auto-Reply or other published flows.

Template Message node (WhatsApp templates)

Use when the bot must send a Meta-approved template (especially outside the 24-hour session window). Configure:

Approved template name and language code
Body placeholders {{1}}, {{2}}, …
Optional header media ID and media type

Trigger keywords

Required for every flow; comma-separated (e.g. help, support, menu).
Set in v2 via Flow Settings; in v1 during save or when creating from a template.
Validated for conflicts with other chatbot flows and Auto-Reply keywords on the same WABA.
Only published + active flows respond to keywords.

Variables

Variables store customer answers and API results for later messages and conditions.

How to write them

v1: Prefer single braces in messages: {customer_name}. The Variable Guide modal inserts system and selection variables.
v2: Properties and examples commonly use double braces: {{customer_name}}, {{user_phone}}.

Common / auto variables (v1 Variable Guide)

System-style: customer_phone, customer_name, timestamp
From buttons/lists: button_response, last_selection, last_selection_title, list_response
Custom names you set on interactive or wait-for-input nodes (e.g. vehicle_type)
Selection history helpers: selection_1, selection_2, …

Use Set Variable (v2) to assign values without waiting for input. Use Wait for Input / button / list variable names to capture customer choices.

Save, auto-save, publish

Action	v1	v2
Save draft	Save Flow	Save (+ auto-save indicator while editing)
Publish	Publish — flow starts responding to keywords	Publish
Unpublish	Unpublish — stops keyword responses	Unpublish

Publishing a draft with invalid or conflicting keywords will fail validation. Fix keywords, then publish again.

Preview and test

v1 Preview: Text outline of the flow path.
v1 Test Flow: Panel to enter a test phone number and message; bot can respond without publishing.
v2 Test: Header Test action for exercising the flow.

After publish, also verify with a real WhatsApp message using a trigger keyword.

Import and export (flows list)

On /chatbot-flows.html (opened from the Chatbot Builder card):

Export — download a flow as JSON (/api/chatbot/flows/:flowId/export)
Import — upload a previously exported JSON file to create/restore a flow
Delete — permanently remove a flow
Publish from the card without opening the editor

Use export for backups and moving flow definitions between environments you control.

Analytics

Portal pages such as chatbot analytics may be available depending on your account navigation. Flow cards on the flows list show created/updated timestamps and published status. For node-level analytics, use the analytics screens linked from your portal when enabled for your account.