Run Group
Start Session1
Start
Start Session1
Integration
Outcome
Send Start
Integration
Telegram Survey Automation Workflow is a 33-node automation blueprint connecting Telegram, Google Sheets, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.
Interactive system map
Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.
33
Nodes
34
Links
2
Run groups
Connected tools
4 integrations
Canvas controls
Fit wide systems, then zoom into any run group.
Signal inspector
Focus, hover, or select a step to isolate its runtime and support links.
Runtime breakdown
Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.
Run Group
Start
Start Session1
Integration
Outcome
Send Start
Integration
Run Group
Start
Telegram Trigger
Trigger
Step 2
Set Variables1
Transform
Step 3
Execution Data2
Integration
Step 4
Get State2
Integration
Step 5
Message Type1
Decision
Step 6
Get Command1
Transform
Get Record1
Integration
Step 7
Bot Actions1
Decision
Has No Record?
Decision
Step 8
Send Start1
Integration
Create Record2
Integration
Get Last Bot Message1
Integration
Step 9
Append Responses1
Transform
Step 10
Should Follow Up?1
AI reasoning
Step 11
Update Answer3
Integration
Interview Agent1
AI reasoning
Step 12
Get State3
Integration
Update Answer2
Integration
Step 13
Get Columns1
Integration
Send Response
Integration
Step 14
Get Survey State1
Transform
Step 15
Increment Index1
Integration
Step 16
Is Survey Continue?
Decision
Step 17
Reset Agent Memory1
AI reasoning
Completed Survey
Integration
Outcome
Send Next Question
Integration
Attached dependencies
These nodes support the runtime above; they are not additional starts or outcomes.
Memory3
AI reasoning dependency
Model3
AI reasoning dependency
Model2
AI reasoning dependency
Memory4
AI reasoning dependency
Turn the map into a plan
Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.