Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

AI-Driven Clinical Assistant Workflow

AI-Driven Clinical Assistant Workflow is a 31-node automation blueprint connecting OpenAI, Google Tasks, Google Calendar. 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.

31

Nodes

30

Edges

4

Zones

AI-Driven Clinical Assistant Workflow execution graphStructural view of 31 workflow nodes and 30 visible connections. Parameters and credentials are intentionally excluded.ZONE 01Intelligence16 NODESZONE 02Intelligence2 NODESZONE 03Entry2 NODESZONE 04Intelligence11 NODESSwitchDECISION / SWITCH21Webhook1TRIGGER / WEBHOOK19Edit Fields1TRANSFORM / SET20OpenAI1AI / OPENAI25AI Agent2AI / AGENT26OpenRouter Chat Model2AI / LMCHATOPENROUTER27Evolution APIINTEGRATION / EVOLUTIONAPI23Convert to FileINTEGRATION / CONVERTTOFILE24Assistente ClínicaAI / AGENT08OpenAI Chat ModelAI / LMCHATOPENAI07Postgres Chat Memory1AI / MEMORYPOSTGRESCH13MCP Google Calendar2AI / MCPCLIENTTOOL14CallToHumanAI / TOOLWORKFLOW29AI AgentAI / AGENT12Evolution API2INTEGRATION / EVOLUTIONAPI28OpenRouter Chat Model1AI / LMCHATOPENROUTER18OpenAIAI / OPENAI22Enviar alerta de cance…INTEGRATION / TELEGRAMTOOL09Receber Mensagem Teleg…TRIGGER / TELEGRAMTRIGGER05Gatilho diárioTRIGGER / SCHEDULETRIGGER10Assistente clinica int…AI / AGENT02TelegramINTEGRATION / TELEGRAM17OpenAI Chat Model1AI / LMCHATOPENAI01Postgres Chat MemoryAI / MEMORYPOSTGRESCH06MCP Google CalendarAI / MCPCLIENTTOOL04Google TasksINTEGRATION / GOOGLETASKSTOOL03Assistente de confirma…AI / AGENT11REMINDERINTEGRATION / EVOLUTIONAPI31OpenAI Chat Model2AI / LMCHATOPENAI30MCP CALENDARAI / MCPCLIENTTOOL16MCP GMAILAI / MCPCLIENTTOOL15
triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.structural metadata only · graph 287064d20b1e7df2

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

3 nodes

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

Receber Mensagem Telegram

Trigger

Gatilho diário

Trigger

Webhook1

Trigger

02

Data & operations

5 nodes

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

Google Tasks

Integration

Enviar alerta de cancelamento

Integration

Edit Fields1

Transform

Evolution API

Integration

Convert to File

Integration

03

Intelligence & routing

20 nodes

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

OpenAI Chat Model1

AI reasoning

Assistente clinica interno

AI reasoning

MCP Google Calendar

AI reasoning

Postgres Chat Memory

AI reasoning

OpenAI Chat Model

AI reasoning

Assistente Clínica

AI reasoning

+ 14 more in system map
04

Terminal actions

3 nodes

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

Telegram

Integration

Evolution API2

Integration

REMINDER

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.