Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

LINE AI Chat & Image Processing Workflow

LINE AI Chat & Image Processing Workflow is a 27-node automation blueprint connecting LINE, Microsoft Teams, Microsoft To Do. Inspect its trigger, execution graph, branches, and implementation requirements.

System map / archived topology

See the whole system without the collisions.

Archived canvas positions are normalized into readable zones. Every visible connector still represents an edge from the source graph.

27

Nodes

26

Edges

5

Zones

LINE AI Chat & Image Processing Workflow execution graphStructural view of 27 workflow nodes and 26 visible connections. Parameters and credentials are intentionally excluded.ZONE 01Entry2 NODESZONE 02Operations8 NODESZONE 03Operations3 NODESZONE 04Operations9 NODESZONE 05Operations5 NODESLine WebhookTRIGGER / WEBHOOK01Line Loading AnimationINTEGRATION / HTTPREQUEST02Microsoft To DoINTEGRATION / MICROSOFTTODO12Microsoft TeamsINTEGRATION / MICROSOFTTEAMS11SwitchDECISION / SWITCH03Get ImageINTEGRATION / HTTPREQUEST04Image RouterAI / AGENT10OpenRouter Chat ModelAI / LMCHATOPENROUTER09Line Reply (Not Suppor…INTEGRATION / HTTPREQUEST08Line Reply (Not Suppor…INTEGRATION / HTTPREQUEST07Line Reply (Text)1INTEGRATION / HTTPREQUEST13Line Reply (Text)INTEGRATION / HTTPREQUEST06If namecardDECISION / IF14Get Image3INTEGRATION / HTTPREQUEST27NamecardExtractAI / AGENT24Microsoft To Do1INTEGRATION / MICROSOFTTODO21OpenRouter Chat Model3AI / LMCHATOPENROUTER23Structured Output ParserAI / OUTPUTPARSERSTRU25Microsoft OneDriveINTEGRATION / MICROSOFTONEDRIV18Microsoft OneDrive1INTEGRATION / MICROSOFTONEDRIV19Get Image2INTEGRATION / HTTPREQUEST20Other ImagesAI / AGENT15Line Reply NamecardINTEGRATION / HTTPREQUEST26HTTP RequestINTEGRATION / HTTPREQUEST22Microsoft Teams1INTEGRATION / MICROSOFTTEAMS16Line Reply (image)INTEGRATION / HTTPREQUEST05OpenRouter Chat Model2AI / LMCHATOPENROUTER17
triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.structural metadata only · graph f9a29bc4a61c70dd

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 Webhook

Trigger

02

Data & operations

11 nodes

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

Line Loading Animation

Integration

Get Image

Integration

Microsoft Teams

Integration

Microsoft To Do

Integration

Microsoft Teams1

Integration

Microsoft OneDrive

Integration

+ 5 more in system map
03

Intelligence & routing

9 nodes

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

Switch

Decision

OpenRouter Chat Model

AI reasoning

Image Router

AI reasoning

If namecard

Decision

Other Images

AI reasoning

OpenRouter Chat Model2

AI reasoning

+ 3 more in system map
04

Terminal actions

6 nodes

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

Line Reply (image)

Integration

Line Reply (Text)

Integration

Line Reply (Not Supported 2)

Integration

Line Reply (Not Supported 1)

Integration

Line Reply (Text)1

Integration

HTTP Request

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
exact
Quality score
14 / 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.