Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Event-Driven AutomationAI systemIntermediate

Line Chatbot Pay Slip Text Extractor

Line Chatbot Pay Slip Text Extractor is a 12-node automation blueprint connecting LINE Messaging API, Google Sheets, Google Gemini. Inspect its trigger, execution graph, branches, and implementation requirements.

LINE Messaging APIGoogle SheetsGoogle Gemini

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

12

Nodes

11

Edges

6

Zones

System stack

3 integrations

  • LINE Messaging API
  • Google Sheets
  • Google AI
Line Chatbot Pay Slip Text Extractor interactive execution graphStructural view of 12 workflow nodes and 11 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Line: Messaging API. trigger node, webhook. 0 incoming and 1 outgoing connections.Line: Messaging APITRIGGERWEBHOOK0 IN / 1 OUTMessage Type. transform node, set. 1 incoming and 1 outgoing connections.Message TypeTRANSFORMSET1 IN / 1 OUTMessage Classification. decision node, switch. 1 incoming and 2 outgoing connections.Message ClassificationDECISIONSWITCH1 IN / 2 OUTGoogle Gemini for Text. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.Google Gemini for TextGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUTLine: Get Image. integration node, httpRequest. 1 incoming and 1 outgoing connections.Line: Get ImageINTEGRATIONHTTPREQUEST1 IN / 1 OUTGoogle Gemini for Image. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.Google Gemini for ImageGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUTText Message Processing. ai node, agent. 3 incoming and 1 outgoing connections.Text Message ProcessingAIAGENT3 IN / 1 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTImage Message Processing. ai node, chainLlm. 2 incoming and 1 outgoing connections.Image Message ProcessingAICHAINLLM2 IN / 1 OUTLine: Text Response to User. integration node, httpRequest. 1 incoming and 0 outgoing connections.Line: Text Response to UserINTEGRATIONHTTPREQUEST1 IN / 0 OUTLine: Response to User. integration node, httpRequest. 1 incoming and 1 outgoing connections.Line: Response to UserINTEGRATIONHTTPREQUEST1 IN / 1 OUTText from Slip Result. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.Text from Slip ResultGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph b0dd63442f97b78dEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

Line: Messaging API

Trigger

02

Data & operations

3 nodes

Transformations and external-system actions that move the work forward.

Line: Get Image

Integration

Message Type

Transform

Line: Response to User

Integration

03

Intelligence & routing

6 nodes

Model calls and control points that interpret, branch, or govern the run.

Window Buffer Memory

AI reasoning

Message Classification

Decision

Text Message Processing

AI reasoning

Image Message Processing

AI reasoning

Google Gemini for Text

AI reasoning

Google Gemini for Image

AI reasoning

04

Terminal actions

2 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Line: Text Response to User

Integration

Text from Slip Result

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
prefix
Quality score
13 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas