Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Featured blueprintBrowse workflows
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.

OpenAIGoogle TasksGoogle CalendarTelegramPostgreSQL

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

31

Nodes

30

Links

3

Run groups

Connected tools

5 integrations

  • OpenAI
  • Google Tasks
  • Google Calendar
  • Telegram
  • PostgreSQL

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Clinical Assistant Workflow execution lanes3 run groups containing 31 workflow nodes and 30 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Receber Mensagem Telegram. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTReceber Mensagem TelegramTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTAssistente clinica interno. ai node, agent. 5 incoming and 1 outgoing connections.STEP 02Assistente clinica internoAIAGENT5 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTPostgres Chat Memory. PostgreSQL node, memoryPostgresChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Postgres Chat MemoryPOSTGRESQLMEMORYPOSTGRESCHAT0 IN / 1 OUTMCP Google Calendar. Google Calendar node, mcpClientTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MCP Google CalendarGOOGLE CALENDARMCPCLIENTTOOL0 IN / 1 OUTGoogle Tasks. integration node, googleTasksTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google TasksINTEGRATIONGOOGLETASKSTOOL0 IN / 1 OUTWebhook1. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhook1TRIGGERWEBHOOK0 IN / 1 OUTEdit Fields1. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit Fields1TRANSFORMSET1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03SwitchDECISIONSWITCH1 IN / 3 OUTOpenAI1. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 04OpenAI1OPENAIOPENAI1 IN / 1 OUTEvolution API. integration node, evolutionApi. 1 incoming and 1 outgoing connections.STEP 04Evolution APIINTEGRATIONEVOLUTIONAPI1 IN / 1 OUTAI Agent2. ai node, agent. 2 incoming and 1 outgoing connections.STEP 05AI Agent2AIAGENT2 IN / 1 OUTConvert to File. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 05Convert to FileINTEGRATIONCONVERTTOFILE1 IN / 1 OUTOpenAI. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 06OpenAIOPENAIOPENAI1 IN / 1 OUTAssistente Clínica. ai node, agent. 8 incoming and 1 outgoing connections.STEP 07Assistente ClínicaAIAGENT8 IN / 1 OUTAI Agent. ai node, agent. 2 incoming and 1 outgoing connections.STEP 08AI AgentAIAGENT2 IN / 1 OUTEvolution API2. integration node, evolutionApi. 1 incoming and 0 outgoing connections.OUTCOMEEvolution API2INTEGRATIONEVOLUTIONAPI1 IN / 0 OUTOpenRouter Chat Model2. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenRouter Chat Model2AILMCHATOPENROUTER0 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTPostgres Chat Memory1. PostgreSQL node, memoryPostgresChat. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Postgres Chat Memory1POSTGRESQLMEMORYPOSTGRESCHAT0 IN / 1 OUTMCP Google Calendar2. Google Calendar node, mcpClientTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MCP Google Calendar2GOOGLE CALENDARMCPCLIENTTOOL0 IN / 1 OUTEnviar alerta de cancelamento. Telegram node, telegramTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Enviar alerta de cancelam…TELEGRAMTELEGRAMTOOL0 IN / 1 OUTCallToHuman. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1CallToHumanAITOOLWORKFLOW0 IN / 1 OUTOpenRouter Chat Model1. ai node, lmChatOpenRouter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenRouter Chat Model1AILMCHATOPENROUTER0 IN / 1 OUTGatilho diário. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTGatilho diárioTRIGGERSCHEDULETRIGGER0 IN / 1 OUTAssistente de confirmação. ai node, agent. 4 incoming and 1 outgoing connections.STEP 02Assistente de confirmaçãoAIAGENT4 IN / 1 OUTREMINDER. integration node, evolutionApi. 1 incoming and 0 outgoing connections.OUTCOMEREMINDERINTEGRATIONEVOLUTIONAPI1 IN / 0 OUTOpenAI Chat Model2. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model2OPENAILMCHATOPENAI0 IN / 1 OUTMCP CALENDAR. ai node, mcpClientTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MCP CALENDARAIMCPCLIENTTOOL0 IN / 1 OUTMCP GMAIL. Gmail node, mcpClientTool. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1MCP GMAILGMAILMCPCLIENTTOOL0 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.31 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

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.

01

Run Group

Receber Mensagem Telegram

2 Execution Links4 Support Dependencies

  1. Start

    Receber Mensagem Telegram

    Trigger

  2. Step 2

    Assistente clinica interno

    AI reasoning

  3. Outcome

    Telegram

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

4 nodes

  • OpenAI Chat Model1

    AI reasoning dependency

  • Postgres Chat Memory

    AI reasoning dependency

  • MCP Google Calendar

    AI reasoning dependency

  • Google Tasks

    Integration dependency

02

Run Group

Webhook1

12 Execution Links7 Support Dependencies

  1. Start

    Webhook1

    Trigger

  2. Step 2

    Edit Fields1

    Transform

  3. Step 3

    Switch

    Decision

  4. Step 4

    OpenAI1

    AI reasoning

    Evolution API

    Integration

  5. Step 5

    AI Agent2

    AI reasoning

    Convert to File

    Integration

  6. Step 6

    OpenAI

    AI reasoning

  7. Step 7

    Assistente Clínica

    AI reasoning

  8. Step 8

    AI Agent

    AI reasoning

  9. Outcome

    Evolution API2

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

7 nodes

  • OpenRouter Chat Model2

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

  • Postgres Chat Memory1

    AI reasoning dependency

  • MCP Google Calendar2

    AI reasoning dependency

  • Enviar alerta de cancelamento

    Integration dependency

  • CallToHuman

    AI reasoning dependency

  • OpenRouter Chat Model1

    AI reasoning dependency

03

Run Group

Gatilho diário

2 Execution Links3 Support Dependencies

  1. Start

    Gatilho diário

    Trigger

  2. Step 2

    Assistente de confirmação

    AI reasoning

  3. Outcome

    REMINDER

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

3 nodes

  • OpenAI Chat Model2

    AI reasoning dependency

  • MCP CALENDAR

    AI reasoning dependency

  • MCP GMAIL

    AI reasoning dependency

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